Which versions of carboniteapp are malicious?

Every published version of carboniteapp on npm is considered malicious. Remove the package entirely.

How do I remediate carboniteapp if I installed it?

carboniteapp is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed carboniteapp — how do I know if it already compromised me?

If carboniteapp 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.

How do I find carboniteapp across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for carboniteapp (all published versions).

Malicious package

carboniteappnpm

Advisory published Nov 10, 2026Updated Nov 12, 2026

carboniteapp is a confirmed malicious npm package (MAL-2026-19151) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in carboniteapp (npm)

MAL-2026-19151

Immediate action

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

npm uninstall carboniteapp

What this malware does

Malicious package. carboniteapp runs an install-time script (node index.js via its npm install hook) that collects host information, resolves the victim's public IP via api.ipify.org, and exfiltrates the collected data to an attacker-controlled Telegram bot (api.telegram.org). No legitimate functionality; the package exists solely to beacon/exfiltrate on install, so all published versions are malicious. Published 2026-05-06 and removed from npm the same day. Full context at the reference below.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for carboniteapp (all published versions).
If you installed it — respond
carboniteapp is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If carboniteapp 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

No. carboniteapp on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

wormsign.io

Credits

wormsign · finder

Detect & block this

O3 blocks carboniteapp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database