Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

disksweepPyPI

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

MAL-2026-6081
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall disksweep

What this malware does

On every import disksweep, the package's top-level src/disksweep/__init__.py (lines 18-24) calls ctypes.CDLL on a 2.9 MB Windows binary (_parser.pyd) shipped inside the wheel. Loading a Windows PE via ctypes.CDLL invokes the DLL's DllMain(DLL_PROCESS_ATTACH) entry point, executing whatever native code the binary contains in the importing process. No Python code in the package ever calls into the DLL — it is loaded purely for its load-time side effects, and any exception is silently swallowed (except: pass). The README explicitly advertises 'Zero dependencies. Nothing to audit.' and the pure-Python scan.py already implements the full scanner functionality, so the binary's presence is unjustified by the advertised feature set. pyproject.toml (lines 87, 90) additionally force-includes a byte-identical copy of the binary under a second name (__parser.pyd, sha256 b1aace6c…f83c3, 2,905,600 bytes) that has no Python reference — a redundancy pattern consistent with AV-evasion / fallback-loading rather than a legitimate native acceleration library. Any Windows host that runs pip install disksweep followed by import disksweep, or invokes the disksweep/sweep CLI (which imports the package), will execute the opaque native code.

During import, package loads embedded native extension module. This library hooks on loading, spawns a new system process and likely attempts to inject the encrypted payload in it for further execution (T1055.012). The code uses heavy analysis evasion techniques. Decrypted payload revealed capabilities to steal all kind of credentials (browsers data, AI tools, env variables, SSH keys, ...), inject code to redirect cryptocurrency transactions, spy-like activities (screenshots, keylogger) and worm-like activities using discovered GitHub tokens to publish malicious code into CI. It establishes persistence in %LOCALAPPDATA%\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe and also attempts to perform lateral movement in Kubernetes and AWS environments.

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

Campaign: 2026-06-syncagents

Reasons (based on the campaign):

  • native-extension

  • infostealer

  • worm

  • exfiltration-crypto

  • exfiltration-credentials

  • uses-telegram-bot

  • keylogger

  • clipboard-stealing

  • exfiltration-ssh-keys

  • The package contains code to detect if it is running in a sandbox environment.

  • obfuscation

  • exfiltration-browser-data

  • exfiltration-env-variables

  • persistence

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

3bc79bc0cdfcad5c0e383a83f621365a84be1090e44364974ee8ec2bf1a12942
5a6449a8f35de848928e7f17d88c87db80e5aee40e8b53c375e07fc7d43cc05e

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for disksweep (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging disksweep across your stack and pipelines.

  2. If you installed it — respond

    disksweep 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.

  3. Did it already run?

    If disksweep 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.

  4. How O3 protects you

    O3 blocks disksweep 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. disksweep on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-06-syncagentsIN-MAL-2026-007035

References

Credits

  • Amazon Inspector · finder
  • Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks disksweep-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.