Which versions of node-calculator-0d96 are malicious?

The following npm versions of node-calculator-0d96 are flagged malicious: 1.0.0, 2.1.0, 3.9.0, 6.6.6. Treat any of these as compromised.

How do I remediate node-calculator-0d96 if I installed it?

Remove node-calculator-0d96 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.

I already installed node-calculator-0d96 — how do I know if it already compromised me?

If node-calculator-0d96 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.

Is node-calculator-0d96 part of a known attack campaign?

Yes — node-calculator-0d96 is associated with the GHSA-mh7x-j32p-xwvh, RLMA-2025-06405, RLUA-2026-01457 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find node-calculator-0d96 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for node-calculator-0d96 (4 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-0d96 across your stack and pipelines.

Malicious package

node-calculator-0d96npm

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

MAL-2025-192400

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall node-calculator-0d96

What this malware does

The package node-calculator-0d96 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

4 flagged

1.0.02.1.03.9.06.6.6

Indicators of compromise (SHA-256)

b4b9ddb05ee502bb8bef628741ba481e4d21f65f46f5604f4bf31efbd95414e9

2a218c7694e38a516577be3b65e74e782080f98629b0cc39516beab80562f57b

92331217add22c795fa271c02a5c5e565e1f3dae021452c46b0a0b3afc3e7d25

2b5d02430a76c225484f17ffe6afe91de69696922defef915ea348fd8615d3a0

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for node-calculator-0d96 (4 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-0d96 across your stack and pipelines.
If you installed it — respond
Remove node-calculator-0d96 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.
Did it already run?
If node-calculator-0d96 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.
How O3 protects you
O3 blocks node-calculator-0d96 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-0d96 on npm has been identified as a malicious package (versions 1.0.0, 2.1.0, 3.9.0, 6.6.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mh7x-j32p-xwvhRLMA-2025-06405RLUA-2026-01457

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks node-calculator-0d96-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