Which versions of sysdiagd are malicious?

The following PyPI versions of sysdiagd are flagged malicious: 1.2.1, 1.2.2, 1.2.3. Treat any of these as compromised.

How do I remediate sysdiagd if I installed it?

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

If sysdiagd was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is sysdiagd part of a known attack campaign?

Yes — sysdiagd is associated with the 2026-10-sysdiagd 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 sysdiagd across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sysdiagd (3 malicious versions).

Malicious package

sysdiagdPyPI

Advisory published Oct 13, 2026Updated Oct 13, 2026

sysdiagd is a confirmed malicious PyPI package (MAL-2026-17861) that steals credentials and exfiltrates sensitive data (malicious versions 1.2.1, 1.2.2, 1.2.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sysdiagd (PyPI)

MAL-2026-17861

Immediate action

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

pip uninstall sysdiagd

What this malware does

Disguised as a system monitoring tool, the package delivers a Discord bot acting as an infostealer exfiltrating credentials, browser data, files and recording audio, screenshots and video. The code requires providing bot credentials, it is not functional without providing them.

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

Campaign: 2026-10-sysdiagd

Reasons (based on the campaign):

rat
exfiltration-browser-data
persistence
exfiltration-credentials
files-exfiltration
spyware-like
infostealer

Malicious versions

3 flagged

1.2.11.2.21.2.3

Indicators of compromise (SHA-256)

0d396ad34176d29956d695014d261847ada859c184d7a8e7820d96087af7eafe

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for sysdiagd (3 malicious versions).
If you installed it — respond
sysdiagd 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 sysdiagd was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. sysdiagd on PyPI has been identified as a malicious package (versions 1.2.1, 1.2.2, 1.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-10-sysdiagd

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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