calcurendernpm
Advisory published Updated
calcurender is a confirmed malicious npm package (MAL-2026-20193) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in calcurender (npm)
What this malware does
On load of the package's main entry (main.js), the module reads a hex blob stored in a field named integrity within package.json, XOR-decodes it with the key 'theskyisbeautiful' sourced from config.json, and after a randomized 0-5 second delay passes the decoded string to child_process.exec. The decoded content begins with 'EXEC_MODE=1; curl -fSL http://...', fetching and executing remote shell content on the host that requires the package. The integrity field name impersonates npm package-lock metadata to disguise the embedded payload; a Mandelbrot computation and a DISCLOSURE file framing the obfuscation as proprietary-algorithm protection serve as cover stories. The README identifies the package as 'calculatoropenerapp' while the actual published name is 'calcurender', a further name-mismatch indicator. Any consumer that require()s or runs this module triggers remote code execution on the installer's machine.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for calcurender (version 1.0.0).
If you installed it — respond
calcurender is a typosquat — you almost certainly intended a legitimately-named package. Remove calcurender, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If calcurender was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks calcurender-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.