simple-node-calc-b
This report shows the evidence for simple-node-calc-b@1.0.0, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-6453 confirms this npm version as malicious.
Advisory
MAL-2026-6453
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in simple-node-calc-b (npm)
Details
simple-node-calc-b@1.0.0 ships a binding.gyp that includes a `modules` file declaring `"lodash": "<!(node lodash-compiler.js)"`. The gyp `<!(...)` syntax executes shell commands at parse time, and npm auto-invokes node-gyp on any package containing binding.gyp during `npm install`, so `node lodash-compiler.js` runs automatically on every install with no user opt-in. lodash-compiler.js is an 87KB obfuscator.io-style packed script (524-entry rotated string array `_0x2f6e`, decoder wrapper, control-flow flattening switch/case dispatcher, hex variable names) reachable through this auto-execution path. The script body contains `require('fs').writeFileSync(...)` along with string-array fragments `'poc.txt'`, `'Security P'`, `'OC.'`, `'writeFileS'`, `'ync'` — self-describing as a proof-of-concept payload. The package name advertises a calculator; there is no legitimate reason for a calculator to ship 87KB of obfuscated code behind a hidden gyp shell-expansion. The combination of auto-execution on default install, heavy obfuscation, purpose mismatch, and self-described POC payload matches the canonical install-time RCE pattern.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to simple-node-calc-b@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing simple-node-calc-b@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.