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

test-mal-npm-pkg-localnpm

Malicious code in test-mal-npm-pkg-local (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1273
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall test-mal-npm-pkg-local

What this malware does

The package test-mal-npm-pkg-local was found to contain malicious 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

1 flagged
1.0.0

Indicators of compromise (SHA-256)

bc1cfed3cc24bd706ec3713fd98d48f9325525419ff04f81eea6f87829a04b85
e75a0b0eec22915db4ca63da2987beda61280504b532ef780e81b26d53e11d8e
b70b20b2fdd43659bb0ce7e3abb1f08b448da0baf50045229b114fada21e733b
790e5cdc93633219beb12137179000e615c7b506267d37c0dd0f3def9f88f8e2

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 test-mal-npm-pkg-local (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-mal-npm-pkg-local across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

GHSA-6258-pr46-j4rcRLMA-2026-01615RLUA-2026-01821

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks test-mal-npm-pkg-local-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
test-mal-npm-pkg-local (npm) malicious package — MAL-2026-1273 | O3 Security