Which versions of requests-core-plugin are malicious?

The following PyPI versions of requests-core-plugin are flagged malicious: 2.31.5, 2.31.6, 2.31.7, 2.31.8, 2.31.9, 2.31.12, 2.31.13, 2.31.14, 2.31.15. Treat any of these as compromised.

How do I remediate requests-core-plugin if I installed it?

requests-core-plugin 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 requests-core-plugin — how do I know if it already compromised me?

If requests-core-plugin 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 requests-core-plugin part of a known attack campaign?

Yes — requests-core-plugin is associated with the 2026-02-requests-core-plugin 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 requests-core-plugin 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 requests-core-plugin (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging requests-core-plugin across your stack and pipelines.

Malicious package

requests-core-pluginPyPI

Malicious code in requests-core-plugin (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-843

Immediate action

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

pip uninstall requests-core-plugin

What this malware does

During installation, package loads obfuscated code that then downloads and starts an executable. The final executable is identified as malware and appears to have infostealer capabilities (collecting browser and Discord data).

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

Campaign: 2026-02-requests-core-plugin

Reasons (based on the campaign):

malware
The package overrides the install command in setup.py to execute malicious code during installation.
impersonation
obfuscation
infostealer

Malicious versions

9 flagged

2.31.52.31.62.31.72.31.82.31.92.31.122.31.132.31.142.31.15

Indicators of compromise (SHA-256)

f7d809caa4cb4961377b3c02a06f90ce19136a36297191248a8c6cd289a809f2

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 requests-core-plugin (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging requests-core-plugin across your stack and pipelines.
If you installed it — respond
requests-core-plugin 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 requests-core-plugin 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 requests-core-plugin 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. requests-core-plugin on PyPI has been identified as a malicious package (versions 2.31.5, 2.31.6, 2.31.7, 2.31.8, 2.31.9, 2.31.12, 2.31.13, 2.31.14, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-02-requests-core-plugin

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks requests-core-plugin-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