Which versions of a-oder are malicious?

The following PyPI versions of a-oder are flagged malicious: 8.0.0. Treat any of these as compromised.

How do I remediate a-oder if I installed it?

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

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

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

Malicious package

a-oderPyPI

Malicious code in a-oder (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12186

Immediate action

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

pip uninstall a-oder

What this malware does

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

Campaign: 2024-07-weaponized-golden

Reasons (based on the campaign):

files-exfiltration

Malicious versions

1 flagged

8.0.0

Indicators of compromise (SHA-256)

7e78ef804d302cbd5d0ad5986dbd24ad8e24217e61933ec02d599510f733ff11

f7e835cce84c3bd2876cea21212f1d41b81ee568e92e90bb0ba1e2c2a1ba1370

0191f4c784e3355272457c61f71e4157245d483bc94a37b1ba2038aab6fb57fd

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

Campaign

2024-07-weaponized-golden

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks a-oder-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