# MAL-2026-5696: Malicious code in voyager-web (npm)


- **Type:** Malicious package
- **Package:** `voyager-web` (npm)
- **Published:** 12 Jun 2026
- **Also known as:** GHSA-3vr9-xc7m-h6qx

## What is MAL-2026-5696?

MAL-2026-5696 is a malicious package in voyager-web, published on 12 Jun 2026. 

### Official description

package.json declares both preinstall and postinstall lifecycle hooks that execute callback.js on `npm install`. callback.js collects installer-side identifiers (os.hostname(), username, uid/gid, homedir, platform, cwd, local IP, external IP via https://api.ipify.org, Node version, package name) and CI environment indicators (presence of GITHUB_TOKEN/AWS_ACCESS_KEY_ID/NPM_TOKEN, GITHUB_REPOSITORY, GITHUB_ACTOR, JENKINS_URL, etc.) and POSTs the JSON payload to a hardcoded Discord webhook at discord.com/api/webhooks/1514602063399747595/<redacted>. A DNS-based exfiltration fallback is also present. The package name typosquats Reddit's open-source `voyager-web` and the version `999.0.0` is the canonical dependency-confusion version-bump used to override an internal/private package of the same name. Self-described as a security research PoC, but the binary effect on any non-consenting installer is automatic exfiltration of host and CI credentials/metadata to an attacker-controlled channel.

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-5696?

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-5696 is a malicious package: voyager-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-5696/ (Markdown: https://insights.sbomify.com/MAL-2026-5696/index.md)
```

## Sources

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

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