Which versions of supervisors are malicious?

The following PyPI versions of supervisors are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate supervisors if I installed it?

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

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

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

Malicious package

supervisorsPyPI

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

MAL-2026-2448

Immediate action

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

pip uninstall supervisors

What this malware does

The setup.py contains a malicious code that skips execution if the system uses Russian language. Otherwise, it downloads the URL of the next stage payload from the Solana blockchain, using the wallet ID associated with the Glossworm campaign. This strongly suggests the owner's account was hijacked. The final payload was not accessible during the analysis.

The malicious code likely originates from the previously hijacked project template in the HydroRoll-Team organization: https://github.com/HydroRoll-Team/pyo3-project-template/blob/975963ca17b9fad49a3a79276c5f8917a0027c2c/setup.py

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

Campaign: 2026-04-supervisors

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
obfuscation

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

c9f99997c1443b3be7bee7a7d490d05077e1d1c48bdd801f7357881ab1a73ca0

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

Campaign

2026-04-supervisors

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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