Which versions of wisecloudsecrets are malicious?

The following PyPI versions of wisecloudsecrets are flagged malicious: 1.4.0. Treat any of these as compromised.

How do I remediate wisecloudsecrets if I installed it?

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

If wisecloudsecrets 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 wisecloudsecrets part of a known attack campaign?

Yes — wisecloudsecrets is associated with the 2026-02-amigapythonupdater, RLMA-2026-00933, RLUA-2026-01691 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 wisecloudsecrets 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 wisecloudsecrets (version 1.4.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wisecloudsecrets across your stack and pipelines.

Malicious package

wisecloudsecretsPyPI

Malicious code in wisecloudsecrets (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-1143

Immediate action

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

pip uninstall wisecloudsecrets

What this malware does

During import, only in specific environments, a module containing code disguised as telemetry is imported. This code then exfiltrates sensitive environment variables and cloud tokens to a hardcoded location, as well as starts a job listening for commands to execute. Likely dependency confusion attempts

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-02-amigapythonupdater

Reasons (based on the campaign):

exfiltration-generic
exfiltration-env-variables
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
dependency-confusion

Malicious versions

1 flagged

1.4.0

Indicators of compromise (SHA-256)

e4ed4357b3e8038ef404e043cc63aafe6484b20d94267c4f024a27d840a4a2fc

bf48353d6e0ef4e773106e035df601cff1beed68d63fc22fc69e5551a79a4764

b8402a6013703f03adff2a8c726cfe89873787ce9483d4e1365cf5381a634814

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 wisecloudsecrets (version 1.4.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wisecloudsecrets across your stack and pipelines.
If you installed it — respond
wisecloudsecrets 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 wisecloudsecrets 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 wisecloudsecrets 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. wisecloudsecrets on PyPI has been identified as a malicious package (version 1.4.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-02-amigapythonupdaterRLMA-2026-00933RLUA-2026-01691

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst
ReversingLabs · finder

Detect & block this

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