Which versions of enquiry-exam are malicious?

The following PyPI versions of enquiry-exam are flagged malicious: 999.999.999. Treat any of these as compromised.

How do I remediate enquiry-exam if I installed it?

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

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

Yes — enquiry-exam is associated with the RLMA-2025-01955, 2025-03-certifications, RLUA-2026-00295 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 enquiry-exam 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 enquiry-exam (version 999.999.999). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging enquiry-exam across your stack and pipelines.

Malicious package

enquiry-examPyPI

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

MAL-2025-2957

Immediate action

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

pip uninstall enquiry-exam

What this malware does

Package contains a reverse shell.

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

Campaign: 2025-03-certifications

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

1 flagged

999.999.999

Indicators of compromise (SHA-256)

1fb5428987e13976324f7d74b9854928db26698ca088876485a6698e0da2a205

3c03261aa6bf1fd320df8108ef85b3531791af04150fab61fe0c617685a35165

590114fe4174abb1ff72c06bf128aef53bd76a67eaeca5d5e891be001f6b0c17

1b9978fc53d66813020ee13aa0a9e56991bf59e0e864a95e3de12a617b46791b

251d2a5d5d0e9dab64026a42902797a05ace8d86bf9170ae6348faef3771ad5a

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

Campaign

RLMA-2025-019552025-03-certificationsRLUA-2026-00295

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks enquiry-exam-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