calcite-webnpm
calcite-web is a confirmed malicious npm package (MAL-2026-15499) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in calcite-web (npm)
What this malware does
package.json at line 11 declares the package's own name as a dependency whose source is the bare URL https://repo.securityctrl.com/calcite-web instead of a registry version range. On npm install, npm fetches whatever tarball that URL returns and installs it with no version pin and no integrity check, executing any lifecycle scripts inside the fetched artifact. The shipped index.js is an inert stub, so the manifest itself is the entire install-time payload, and whoever controls repo.securityctrl.com controls code that runs on every installer. The dependency key equals the package's own name (dependency-confusion shape), and the implausibly high version (45.0.0) is consistent with an override attempting to win resolution against an internal package of the same name.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for calcite-web (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging calcite-web across your stack and pipelines.
If you installed it — respond
Remove calcite-web 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 calcite-web 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 calcite-web 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks calcite-web-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.