Which versions of discould are malicious?

The following PyPI versions of discould are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate discould if I installed it?

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

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

Yes — discould is associated with the RLMA-2024-11028, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00276 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 discould 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 discould (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging discould across your stack and pipelines.

Malicious package

discouldPyPI

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

MAL-2024-11578

Immediate action

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

pip uninstall discould

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2ebefe7c01e51837216afb24515d52e8f2e3ef40950484ce03dca559e6fa1ced

4424a97d3bdb8eb365f0a7484f0f2a760c30c0cdd0c369e0a0f3e6ead9fb418e

bb38a630a1e0c6e81089ebb95d407d438c932c26527fde69e9c304305d267ca9

a3d9cb3ff1a1e23729c8f546a15c47ae68b5caf4fba54863827d766d5c9f438e

2cec5eb9c102e1d8661bd7004a3d0cf85f15205063e573a0d5e2325fe4df7583

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

Campaign

RLMA-2024-110282024-08-embeds-RealtekHDAudioManagerRLUA-2026-00276

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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