Which versions of pyjio are malicious?

The following PyPI versions of pyjio are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate pyjio if I installed it?

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

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

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

Malicious package

pyjioPyPI

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

MAL-2023-8576

Immediate action

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

pip uninstall pyjio

What this malware does

Malicious packages campaign targeting developers, payload is hidden using Steganography, exfiltrate host information

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

26d9b6377460b59c1e31da04bf9acd401bd082c4911c43dbe41a60d55d65904a

c599785ca8079b21b86b4d6d6fe5f150b0ea55a5a87b6f892147293b06b9b976

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

Campaign

RLMA-2024-04516

References

Credits

Checkmarx · finder
ReversingLabs · finder

Detect & block this

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