NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

test-dev-linknpm

Advisory published Updated

test-dev-link is a confirmed malicious npm package (MAL-2026-11492) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-dev-link (npm)

MAL-2026-11492
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall test-dev-link

What this malware does

No static or traced behavioral signals of supply-chain attack were observed in this package. There is no evidence of install-time or import-time code execution beyond ordinary package contents, no credential or environment scraping, no network exfiltration to attacker-controlled destinations, no dropper, no silent-relay, and no backdoor mechanism. The package name and version suggest a small or test/utility release.

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

1 flagged
0.1.0

Indicators of compromise (SHA-256)

753c40af198c777d7248e2e3f9c4df1ffdb26e7acecb35a05c76c38dfc07bc74
be4f4885b543da795140d0ac9c44423c6ecadf74c744c1f322f9d1a5263fe4f2

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for test-dev-link (version 0.1.0).

  2. If you installed it — respond

    test-dev-link is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If test-dev-link 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-dev-link on npm has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vf2p-478v-vg76IN-MAL-2026-013339

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks test-dev-link-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

test-dev-link (npm) malicious package — MAL-2026-11492 | O3 Security