Which versions of carbonite-internal are malicious?

The following npm versions of carbonite-internal are flagged malicious: 99.9.0. Treat any of these as compromised.

How do I remediate carbonite-internal if I installed it?

Remove carbonite-internal 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 carbonite-internal — how do I know if it already compromised me?

If carbonite-internal 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 carbonite-internal across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for carbonite-internal (version 99.9.0).

Malicious package

carbonite-internalnpm

Advisory published May 6, 2026Updated May 12, 2026

carbonite-internal is a confirmed malicious npm package (MAL-2026-3352) that executes malicious code on install (malicious version 99.9.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in carbonite-internal (npm)

MAL-2026-3352

Immediate action

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

npm uninstall carbonite-internal

What this malware does

The package carbonite-internal was found to contain malicious code.

The OpenSSF Package Analysis project identified 'carbonite-internal' @ 99.9.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.9.0

Indicators of compromise (SHA-256)

9187d7e1d292c21fa0cb37a0ef02fbc1ebcd489eb60d2bc753329f0f27d275ee

4fec002c13bf1ef1b49658e5dc490ca30515cf414294154827adadab04cbc234

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for carbonite-internal (version 99.9.0).
If you installed it — respond
Remove carbonite-internal 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 carbonite-internal 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. carbonite-internal on npm has been identified as a malicious package (version 99.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks carbonite-internal-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

Explore

All malware advisories How O3 detects malware Vulnerability database