Which versions of bh-usa-automate-req-ase are malicious?

The following PyPI versions of bh-usa-automate-req-ase are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate bh-usa-automate-req-ase if I installed it?

bh-usa-automate-req-ase 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 bh-usa-automate-req-ase — how do I know if it already compromised me?

If bh-usa-automate-req-ase 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 bh-usa-automate-req-ase part of a known attack campaign?

Yes — bh-usa-automate-req-ase is associated with the 2025-07-jsonreq-ase 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 bh-usa-automate-req-ase 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 bh-usa-automate-req-ase (version 0.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bh-usa-automate-req-ase across your stack and pipelines.

Malicious package

bh-usa-automate-req-asePyPI

Malicious code in bh-usa-automate-req-ase (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191691

Immediate action

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

pip uninstall bh-usa-automate-req-ase

What this malware does

If run, the package exfiltrates AWS credentials. Though it's described as test, the exfiltration really happens

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

Campaign: 2025-07-jsonreq-ase

Reasons (based on the campaign):

exfiltration-credentials

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

0ee7247ffe689db99c4bfa5daa5899d0ab0e26933bd420ac931ceeb2aa89fb55

b0340aadb507418f2d21cfa7d568f133db23a6392a2ec64411540ec4ce5456d7

9a9ef628b94b71dcd1c877691a313336f56ca2e47db0eef76748d0639f3c1ef2

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

Campaign

2025-07-jsonreq-ase

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks bh-usa-automate-req-ase-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