Which versions of axonify are malicious?

The following PyPI versions of axonify are flagged malicious: 1.0, 6.2, 7.6, 8.0, 8.5, 9.0, 10.0. Treat any of these as compromised.

How do I remediate axonify if I installed it?

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

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

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

Malicious package

axonifyPyPI

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

MAL-2025-191688

Immediate action

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

pip uninstall axonify

What this malware does

The package is capable of installing malware from a hardcoded URL. The malware is well-recognized and acts as infostealer. Interestingly, it uses Steam profiles to get the current C2 domain (based on sandbox analysis).

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

Campaign: 2025-03-logax

Reasons (based on the campaign):

infostealer
malware

Malicious versions

7 flagged

1.06.27.68.08.59.010.0

Indicators of compromise (SHA-256)

18750101071446d59ebfb47402bdf49a6d5adf9ff2482f5cd735e59787cdec72

22991c04631c7553b040a72573bc7d0ad80886ab6bc834ac43f1e1611f85ea02

1340be50ea1782d5b4e435dbdaeae4e50ded6272850772c2cc3bb8acac5ea32b

4971089247edf555cafc9a8a81777da6a11bbd10b67acc05ef183b3987fb83c9

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

Campaign

2025-03-logax

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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