Which versions of pyioapso are malicious?

The following PyPI versions of pyioapso are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate pyioapso if I installed it?

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

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

Yes — pyioapso is associated with the RLMA-2024-04513 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 pyioapso 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 pyioapso (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 pyioapso across your stack and pipelines.

Malicious package

pyioapsoPyPI

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

MAL-2023-8574

Immediate action

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

pip uninstall pyioapso

What this malware does

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

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ddface0422e0d25912e1810f515798f9258e861b2f6d89a9514856d598a5395f

967a32abfb6b94330dd206dd70ada98f2fadf397703b42a2fa81149f509f6448

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 pyioapso (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 pyioapso across your stack and pipelines.
If you installed it — respond
pyioapso 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 pyioapso 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 pyioapso 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. pyioapso 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

RLMA-2024-04513

References

Credits

Checkmarx · finder
ReversingLabs · finder

Detect & block this

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