What does the wiki-requests malware do?

Setup.py attempts to exfiltrate information about the system and span a reverse shell Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-03-wiki-requests 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. - exfiltration-generic - The package overrides the install command in setup.py to execute malicious code during installation.

Which versions of wiki-requests are malicious?

The following PyPI versions of wiki-requests are flagged malicious: 0.0.1, 0.0.2, 0.0.3. Treat any of these as compromised.

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

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

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

Yes — wiki-requests is associated with the RLMA-2025-02018, 2025-03-wiki-requests, RLUA-2026-00930 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 wiki-requests 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 wiki-requests (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wiki-requests across your stack and pipelines.

Malicious package

wiki-requestsPyPI

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

MAL-2025-3019

Immediate action

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

pip uninstall wiki-requests

What this malware does

Setup.py attempts to exfiltrate information about the system and span a reverse shell

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

Campaign: 2025-03-wiki-requests

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.
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

3 flagged

0.0.10.0.20.0.3

Indicators of compromise (SHA-256)

e73c711369bea9a57b1db2fd56b1bebb612fad1c694da9147c918d96b022fe28

a5d6f03266e01e339a10713b7cdfb1790beeb6ff351e3aa5d320389f2ce30dfe

9d4143f13c89e66e8f5b2c0905a57d6d25f6d02d46b62aef3e58d4b1f2dda697

a5d7d773f86d2e4292db788e2afe5c9bd1cc7e714622b893108ba2707e19ca09

794265c17b9f0de671b4730331b4de3bd0473f5a1a395f446b25caf360c160e3

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

Campaign

RLMA-2025-020182025-03-wiki-requestsRLUA-2026-00930

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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