Which versions of anduril-sdk are malicious?

The following PyPI versions of anduril-sdk are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate anduril-sdk if I installed it?

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

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

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

Malicious package

anduril-sdkPyPI

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

MAL-2026-2083

Immediate action

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

pip uninstall anduril-sdk

What this malware does

During installation or import, the package exfiltrates basic information in a dependency confusion attempt. The user identifies themselves as a HackerOne user abusing the PyPI for the purpose of a bug bounty program.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-hackerone-bugbounty

Reasons (based on the campaign):

dependency-confusion
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

a5cbc3053e38d3280b6e93548f32f64751b0499f79b439459b733d4ca88b426f

cee84e8a324e29cf571479dda523d4b5a0f9d16ef6b9810320bf0b438ab81b2f

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

Campaign

GENERIC-hackerone-bugbounty

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks anduril-sdk-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