Which versions of oracle-lag-sniper are malicious?

The following PyPI versions of oracle-lag-sniper are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate oracle-lag-sniper if I installed it?

oracle-lag-sniper 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 oracle-lag-sniper — how do I know if it already compromised me?

If oracle-lag-sniper 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 oracle-lag-sniper part of a known attack campaign?

Yes — oracle-lag-sniper is associated with the 2026-05-oracle-lag-sniper 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 oracle-lag-sniper 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 oracle-lag-sniper (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oracle-lag-sniper across your stack and pipelines.

Malicious package

oracle-lag-sniperPyPI

Malicious code in oracle-lag-sniper (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3223

Immediate action

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

pip uninstall oracle-lag-sniper

What this malware does

When using the package, it exfiltrates sensitive environmental variables (targeting Polymarket keys) to the target controlled via a Polymarket's user profile. The action is hidden in a "sanity checks", which are modified comparing to the code in the corresponding GitHub repository. Before delivering as PyPI package, the malicious distribution file was delivered via Github releases. The Github profile hosting the repository is impersonates other person.

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

Campaign: 2026-05-oracle-lag-sniper

Reasons (based on the campaign):

exfiltration-env-variables
crypto-related
impersonation

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

052e2309a320b056b5a959c33b703d819b1fa2ce9b2647d250bc612d25bae9c9

7167dc6c2e31d6b7499e6b7d452dc7310000ebc5279c7f85bfcadddda19437ac

d83b8937e90443afa11cfb26e619b7b1f4e011931c3e4d615e98c64ce82a424d

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

Campaign

2026-05-oracle-lag-sniper

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks oracle-lag-sniper-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