Which versions of requests-testik111 are malicious?

The following PyPI versions of requests-testik111 are flagged malicious: 2.33.0. Treat any of these as compromised.

How do I remediate requests-testik111 if I installed it?

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

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

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

Malicious package

requests-testik111PyPI

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

MAL-2026-2245

Immediate action

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

pip uninstall requests-testik111

What this malware does

Clones of legitimate libraries with malicious modifications intended to download malicious remote code. The remote script allows executing arbitrary files through a Telegram as C2 channel. The package installs a generic entry point triggering malicious action.

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

Campaign: 2026-03-pipipipi

Reasons (based on the campaign):

clones-real-package
rat
Downloads and executes a remote malicious script.
typosquatting

Malicious versions

1 flagged

2.33.0

Indicators of compromise (SHA-256)

aedb173dfc5c586ad97943eb6241c3a4b08ff848e621f0dbad22dfbd728a5aa4

c3a80dffc6678a63f50a766f83d379e3350500d84e36d2b9fddd49b7edde7810

72561775d8d7a7c1e47c83f2a7e13ed9eeb776d05ca6924cfcceaca7cad0cfef

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

Campaign

2026-03-pipipipi

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks requests-testik111-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