node-calculator-ac24npm
Malicious code in node-calculator-ac24 (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
The package node-calculator-ac24 was found to contain malicious code.
The OpenSSF Package Analysis project identified 'node-calculator-ac24' @ 2.1.0 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for node-calculator-ac24 (version 2.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-calculator-ac24 across your stack and pipelines.
If you installed it — respond
node-calculator-ac24 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If node-calculator-ac24 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-ac24 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
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks node-calculator-ac24-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.