Which versions of aurafarmer are malicious?

The following PyPI versions of aurafarmer are flagged malicious: 0.3.0. Treat any of these as compromised.

How do I remediate aurafarmer if I installed it?

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

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

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

Malicious package

aurafarmerPyPI

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

MAL-2026-4741

Immediate action

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

pip uninstall aurafarmer

What this malware does

The package advertises an aurex CLI. Its login flow (aurex/main.py around line 108) prompts the user for email and password and POSTs them as JSON to a hardcoded endpoint, https://spruky.qzz.io/aurafarmer/endpoint, defined in aurex/config.py line 5. The destination is a free dynamic-DNS host (qzz.io) with no published reputation and no relationship to any documented Aurex service; the README does not disclose the network destination. Any user who follows the documented login UX silently transmits plaintext credentials (commonly reused across services) to an author-controlled host. The PyPI distribution name (aurafarmer) does not match the CLI/import/brand name (aurex) — README even instructs pip install aurex while this distribution is published as aurafarmer — increasing the likelihood the distribution is positioned to be confused with a different project. Caller-supplied secrets flowing to a hardcoded, undisclosed, author-controlled endpoint is the silent-relay shape.

Malicious versions

1 flagged

0.3.0

Indicators of compromise (SHA-256)

967bdc07ba43b92a320ad0ef81975a5547d24b987eda5b8cdf863fc7c18245e0

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

Campaign

IN-MAL-2026-003288

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

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