Which versions of cloudpivot are malicious?

The following npm versions of cloudpivot are flagged malicious: 1.0.1, 1.0.3. Treat any of these as compromised.

How do I remediate cloudpivot if I installed it?

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

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

Is cloudpivot part of a known attack campaign?

Yes — cloudpivot is associated with the IN-MAL-2026-004300, IN-MAL-2026-004299 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cloudpivot (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cloudpivot across your stack and pipelines.

Malicious package

cloudpivotnpm

Malicious code in cloudpivot (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4529

Immediate action

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

npm uninstall cloudpivot

What this malware does

On npm install, the package.json preinstall hook runs wget against http://194.120.24.50:7374 with query parameters carrying $(whoami), $(pwd), $(hostname), and a base64-encoded copy of /etc/passwd. The package ships no functional code — main: index.js is declared but no index.js is present — so the only effect of installing the package is the exfiltration probe firing automatically. The destination is a bare IP over plain HTTP, with no relation to any declared publisher, and the package description itself references Burp Collaborator abuse. Any developer or CI system that runs npm install cloudpivot leaks host identifiers and the local user database to the operator of 194.120.24.50.

Malicious versions

2 flagged

1.0.11.0.3

Indicators of compromise (SHA-256)

4bd95ac92732da86e3ec63771e124da83ea8d98e1dd2f6636ab3d8dde76ab34c

e9fbe3aa0aad306420c2f7b34389ded8e1fc6e044a2af36789935051475f5284

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cloudpivot (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cloudpivot across your stack and pipelines.
If you installed it — respond
cloudpivot 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 cloudpivot 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 cloudpivot 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

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

Campaign

IN-MAL-2026-004300IN-MAL-2026-004299

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cloudpivot-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