Which versions of hackerone-app-sdk are malicious?

The following PyPI versions of hackerone-app-sdk are flagged malicious: 0.17.0, 0.18.0, 0.19.1. Treat any of these as compromised.

How do I remediate hackerone-app-sdk if I installed it?

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

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

Yes — hackerone-app-sdk is associated with the RLMA-2025-05211, GENERIC-standard-pypi-install-pentest, RLUA-2026-00372 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 hackerone-app-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 hackerone-app-sdk (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hackerone-app-sdk across your stack and pipelines.

Malicious package

hackerone-app-sdkPyPI

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

MAL-2025-48892

Immediate action

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

pip uninstall hackerone-app-sdk

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

3 flagged

0.17.00.18.00.19.1

Indicators of compromise (SHA-256)

afbe6bddcd85abd24300f735ee11fffa58ee409b2d1297033700b8050ac28bc2

ec9f5e3b9a5854f28db5438f9967e21b65574188e6872860ed084132f7a97b71

7989720a786925f09101ea3e9ebce9bf8190a57a6401b6e46125a75ad160bc66

0cfb46a3c4d57362d8cae555161436c78a9dc673c0daeae0b501faa5c248eca4

194f5dc3a4b9a652fe0db796a81814f5fbbb5e69b8b96bf8572ad813e9f7c484

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

Campaign

RLMA-2025-05211GENERIC-standard-pypi-install-pentestRLUA-2026-00372

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks hackerone-app-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