Which versions of discconnect are malicious?

The following PyPI versions of discconnect are flagged malicious: 0.1, 0.2, 0.4, 0.5. Treat any of these as compromised.

How do I remediate discconnect if I installed it?

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

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

Yes — discconnect is associated with the RLMA-2024-11024, 2024-11-discconnect, RLUA-2026-00266 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 discconnect 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 discconnect (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging discconnect across your stack and pipelines.

Malicious package

discconnectPyPI

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

MAL-2024-11576

Immediate action

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

pip uninstall discconnect

What this malware does

During installation, a remote, obfuscated executable is downloaded and started. The executable at least disables automated updates, malware protection and other security mechanisms.

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

Campaign: 2024-11-discconnect

Reasons (based on the campaign):

typosquatting
The package overrides the install command in setup.py to execute malicious code during installation.
Downloads and executes a remote executable.
modify-system-without-consent

Malicious versions

4 flagged

0.10.20.40.5

Indicators of compromise (SHA-256)

91c782a1506ffdfc72660332a03b6a0c66759e06754d3ff90c9b87d36a836cd1

14c1b7e2d60eeed63069cbd161e469d2b6c45f90cf646b050bfd40c9685ccc74

cd96a216a1790b73568af638b97003c7abd1f502c962137cd1084fb48ebcca64

9d46d3a98e6ff1fb35389291690a110a3f6e942c7cd65baffc827d73e8d738fe

c659836c1e6cbe02a2bbc1920c934aeee24125715b50a751026f275948efb8fa

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

Campaign

RLMA-2024-110242024-11-discconnectRLUA-2026-00266

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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