Which versions of darkglitch are malicious?

The following PyPI versions of darkglitch are flagged malicious: 1.2.0, 1.2.9. Treat any of these as compromised.

How do I remediate darkglitch if I installed it?

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

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

Yes — darkglitch is associated with the IN-MAL-2026-010758, IN-MAL-2026-010855 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 darkglitch 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 darkglitch (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging darkglitch across your stack and pipelines.

Malicious package

darkglitchPyPI

darkglitch is a confirmed malicious PyPI package (MAL-2026-10756) that steals credentials and exfiltrates sensitive data (malicious versions 1.2.0, 1.2.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in darkglitch (PyPI)

MAL-2026-10756

Immediate action

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

pip uninstall darkglitch

What this malware does

The package installs a listener CLI (darkglitch -l -b) that opens a WebSocket to the hardcoded signaling host malware-signal.vercel.app and joins the hardcoded room D4RKGLI7CH (core/data/client.py: HOST/ROOM constants). Incoming remote-command messages are executed on the host via subprocess.run(command, shell=True, capture_output=True,...) inside _process_command_request, with stdout/stderr returned to the sender. transfer_utils/transfer.py extends this channel with arbitrary file upload/download: build_transfer_command emits a python3 heredoc that base64-encodes any source path's bytes for exfiltration, and the upload branch base64-decodes attacker-supplied bytes to any target path. The README instructs users to build the listener as darkglitch_listener.exe with PyInstaller's --noconsole flag so no window appears, and internal modules (malware_signal, injection_utils, helper.py) describe themselves as a "post-exploitation framework" and "Advanced Command & Control Framework". The room identifier is shared, so any party who knows it can issue commands to any host running the listener.

Malicious versions

2 flagged

1.2.01.2.9

Indicators of compromise (SHA-256)

6d02eb8be388433532783a7bf88864824b50756b7ced4f8728721866740c5df1

5a84fec55fc625d5e2b337aafe5a9a95ff30c47403241c59dbb33543ec97311a

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

Campaign

IN-MAL-2026-010758IN-MAL-2026-010855

References

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database