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

test-mal-npm-pkg-not-localnpm

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

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

What this malware does

The package test-mal-npm-pkg-not-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)

7358cb2f6bb83372c6ef7f6f304d5c66749386c13e3be7efaea4f1751c73733c
803f42bec3cf0ba231262e882d9fb5def7e78c005b10e0c32edf60aecad5d9bf
27bb9f5ef2bd0788d0659c1ea62406aa47b63f2c46cc9f526b35c7d7d84c9690
c62eb5898c750b3dceb9f6b9a7fef7b844cf1205689d080b5401e5810784c8cd

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-not-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-not-local across your stack and pipelines.

  2. If you installed it — respond

    Remove test-mal-npm-pkg-not-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-not-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-not-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-not-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-5q4h-v7c2-v9r2RLMA-2026-01616RLUA-2026-01822

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

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