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

source-analyzernpm

source-analyzer is a confirmed malicious npm package (MAL-2026-14013) that executes malicious code on install (malicious versions 0.5.7, 0.5.8, 0.5.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in source-analyzer (npm)

MAL-2026-14013
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall source-analyzer

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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

3 flagged
0.5.70.5.80.5.9

Indicators of compromise (SHA-256)

4f22d4c665b725a284e55958481919ef0b1a0514172e5c3417cd915700c6ca76
17c2f07bb4a673bf18d866e697b1a943783696d2871fbc5e5987c2117377e798
22f04ad16297e96f12fa48ef5d74524c1d6c3eaeb8fbf045cabd34ebf6a70d27
ca899176b57245641b601be48df49fd70ee373ce03766ae651127362e7507028

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 source-analyzer (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging source-analyzer across your stack and pipelines.

  2. If you installed it — respond

    Remove source-analyzer 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 source-analyzer 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 source-analyzer 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. source-analyzer on npm has been identified as a malicious package (versions 0.5.7, 0.5.8, 0.5.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p68g-6893-44r8IN-MAL-2026-017886IN-MAL-2026-017888IN-MAL-2026-017884

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks source-analyzer-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.

Explore

source-analyzer (npm) malicious package — MAL-2026-14013 | O3 Security