Which versions of simple-node-calc-ccc are malicious?

The following npm versions of simple-node-calc-ccc are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate simple-node-calc-ccc if I installed it?

Remove simple-node-calc-ccc 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 simple-node-calc-ccc — how do I know if it already compromised me?

If simple-node-calc-ccc 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 simple-node-calc-ccc part of a known attack campaign?

Yes — simple-node-calc-ccc is associated with the IN-MAL-2026-007502 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 simple-node-calc-ccc 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 simple-node-calc-ccc (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 simple-node-calc-ccc across your stack and pipelines.

Malicious package

simple-node-calc-cccnpm

Malicious code in simple-node-calc-ccc (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6455

Immediate action

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

npm uninstall simple-node-calc-ccc

What this malware does

Package name 'simple-node-calc-ccc' presents as a trivial calculator but ships lodash-compiler.js, an 87KB obfuscator.io-packed file using rotating string-array decoding (_0xNNNN identifiers, _0x2f6e rotation table). The decoded payload calls require('fs')['writeFileS'+'ync']('poc.txt', 'Security P...OC.'). The package also ships a non-standard config.gypi (line 9) containing "action": ["node", "lodash-compiler.js"]. config.gypi is normally generated locally by node-gyp configure and is not shipped with packages; shipping a hand-crafted config.gypi with a custom action that invokes an obfuscated sibling script is a covert mechanism to execute the obfuscated file whenever any downstream tool runs node-gyp in the package directory. While the present payload only writes a marker file ('Security POC'), the technique itself ships arbitrary obfuscated code execution to any installer who triggers a node-gyp build in this tree, and the obfuscation has no legitimate purpose for a calculator package.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f9bfe35484999f40374a6dcfea11247cf3407a3177e27506c714407b9384036a

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 simple-node-calc-ccc (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 simple-node-calc-ccc across your stack and pipelines.
If you installed it — respond
Remove simple-node-calc-ccc 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 simple-node-calc-ccc 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 simple-node-calc-ccc 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. simple-node-calc-ccc 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

IN-MAL-2026-007502

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks simple-node-calc-ccc-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