# MAL-2026-6361: Malicious code in vscode-test-web (npm)


- **Type:** Malicious package
- **Package:** `vscode-test-web` (npm)
- **Published:** 24 Jun 2026
- **Also known as:** GHSA-vxwh-gqjr-fxcw

## What is MAL-2026-6361?

MAL-2026-6361 is a malicious package in vscode-test-web, published on 24 Jun 2026. 

### Official description

Package occupies the unscoped npm name `vscode-test-web`, a likely-misreference target for the legitimate `@vscode/test-web` scoped package. On `require()`, `index.js` prints a banner derived from `os.platform()` and `os.hostname()` and then calls `process.exit(0)` at line 42, which terminates any host process that imports it. The package's own metadata (package.json description) declares the upload as a security-research proof-of-concept squat for an MSRC bug-bounty report. There is no network I/O, no shell execution, no credential or filesystem read, and no install-time lifecycle hook — the only installer-side effect is the abrupt process termination on import, which would break a build that mistakenly resolves this name instead of `@vscode/test-web`. Name-confusion risk is real but intent appears non-malicious; routing for human adjudication.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## What should I do about MAL-2026-6361?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6361 is a malicious package: vscode-test-web (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-6361/ (Markdown: https://insights.sbomify.com/MAL-2026-6361/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6361

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6361/
Summaries are generated and may contain mistakes; the official description above is the record.