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

node-calculator-x7k9npm

Malicious code in node-calculator-x7k9 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190547
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall node-calculator-x7k9

What this malware does

The package node-calculator-x7k9 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.

The OpenSSF Package Analysis project identified 'node-calculator-x7k9' @ 3.4.0 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged
3.1.03.4.0

Indicators of compromise (SHA-256)

61652e0e15358217e6b9754390cba499bb2411fe1815da0ff1f39f5fde071478
cd96e874bd4c6ec650ccc8071bd0d017a4952e253ab3bac44c5802368b34df6e
c4516f9cca556d86ef615dcd51bf2741cf6f96d329092a3333f9dcab63682371
8c91310af95df1bdaaf930ec5de87bb4cdf3cca17a615ab73336d2841052912f

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

  2. If you installed it — respond

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

Campaign

GHSA-f23r-hrcx-5m33

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks node-calculator-x7k9-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.

node-calculator-x7k9 (npm) malicious package — MAL-2025-190547 | O3 Security