Which versions of cloudera are malicious?

The following npm versions of cloudera are flagged malicious: 99.9.10. Treat any of these as compromised.

How do I remediate cloudera if I installed it?

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

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

Search your lockfiles and build artifacts for cloudera (version 99.9.10).

Malicious package

clouderanpm

Advisory published Apr 5, 2026Updated Apr 7, 2026

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

Malicious code in cloudera (npm)

MAL-2026-2495

Immediate action

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

npm uninstall cloudera

What this malware does

The package cloudera was found to contain malicious code.

The OpenSSF Package Analysis project identified 'cloudera' @ 99.9.10 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.9.10

Indicators of compromise (SHA-256)

5596ceaf93b1fe8c288cd536d4c4a1fee9d0fec028756fdadbb4365630e9eb2a

11ddf3c5a1eb28ca1531748670bd932bda38d78b04ae81c983361465a2076f57

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for cloudera (version 99.9.10).
If you installed it — respond
Remove cloudera 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 cloudera 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. cloudera on npm has been identified as a malicious package (version 99.9.10 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 cloudera-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