Which versions of oe-extract-ids are malicious?

The following PyPI versions of oe-extract-ids are flagged malicious: 0.1, 0.1.40, 0.1.50, 1.5.0, 1.5.1. Treat any of these as compromised.

How do I remediate oe-extract-ids if I installed it?

oe-extract-ids 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 oe-extract-ids — how do I know if it already compromised me?

If oe-extract-ids 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 oe-extract-ids part of a known attack campaign?

Yes — oe-extract-ids is associated with the GENERIC-standard-pypi-install-pentest 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 oe-extract-ids 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 oe-extract-ids (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oe-extract-ids across your stack and pipelines.

Malicious package

oe-extract-idsPyPI

Malicious code in oe-extract-ids (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12316

Immediate action

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

pip uninstall oe-extract-ids

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

5 flagged

0.10.1.400.1.501.5.01.5.1

Indicators of compromise (SHA-256)

e87fd99c50d754e4a0de0d4694123e2ea1c7cea2b3fe0e7cf38e4ca14847557a

bebbe22a538c4b7b6688bd82facdd749052e801663cf523c8d9c1eb11f81ea57

5e3a9da53a43e9f5f826582915787b7709a1fc06d85e816dff426da3a6f01feb

5fbe8e0c51aeab8ce5ba91e81cbd65171044eed3a45c701e312862fddfa26cf5

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

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks oe-extract-ids-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