Which versions of ase-jreq are malicious?

The following PyPI versions of ase-jreq are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate ase-jreq if I installed it?

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

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

Yes — ase-jreq 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 ase-jreq 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 ase-jreq (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 ase-jreq across your stack and pipelines.

Malicious package

ase-jreqPyPI

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

MAL-2025-191684

Immediate action

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

pip uninstall ase-jreq

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)

156c0206b969e9f1b6e4476e5c5e779d7a85329033ba1f7945486ff83e70c95d

53d3ded73c297df3a6a010b08188ed7b3fab13570e8d72492803ae3903a49939

0d31df37128071ee076d366870d507699cb1594d97a272146364a99d68ffc464

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 ase-jreq (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 ase-jreq across your stack and pipelines.
If you installed it — respond
ase-jreq 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 ase-jreq 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 ase-jreq 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. ase-jreq 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 ase-jreq-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