Which versions of sunrequests are malicious?

The following PyPI versions of sunrequests are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate sunrequests if I installed it?

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

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

Yes — sunrequests is associated with the RLMA-2024-11175, 2024-09-sunrequests, RLUA-2026-00787 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 sunrequests 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 sunrequests (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sunrequests across your stack and pipelines.

Malicious package

sunrequestsPyPI

Malicious code in sunrequests (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11716

Immediate action

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

pip uninstall sunrequests

What this malware does

Running the module starts an infostealer attempting to exfiltrate credentials from webbrowsers

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

Campaign: 2024-09-sunrequests

Reasons (based on the campaign):

infostealer
A Telegram webhook is used to send collected data.
dependency-confusion

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

57dac716ea0a53f73a2a35f4c60a8981b3d2cdcc8f39ff53c9b33ddaaeb4b696

d3265a4b941339c7a8b35ce5b7f92d3362821768e3f455672751bcfcabbfefe6

314b140727c2d65586134b9e2722bdbba66be25e0f391d1b886cc08824783c63

00d84a989222c1beecdac2915f0d237ac14da98e88f3bd49a10dbfd8e17dcdd3

284ba1536b4e30f17a9b531eba746983ae6e240f2fd3146c07898491229506b7

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

Campaign

RLMA-2024-111752024-09-sunrequestsRLUA-2026-00787

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks sunrequests-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