Which versions of set7 are malicious?

The following PyPI versions of set7 are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.4, 1.0.5, 1.0.7. Treat any of these as compromised.

How do I remediate set7 if I installed it?

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

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

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

Malicious package

set7PyPI

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

MAL-2025-41760

Immediate action

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

pip uninstall set7

What this malware does

Package downloads and suggest opening an obfuscated script, which is an infostealer

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

Campaign: 2025-07-set7

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
crypto-related
infostealer
exfiltration-crypto

Malicious versions

6 flagged

1.0.01.0.11.0.21.0.41.0.51.0.7

Indicators of compromise (SHA-256)

5066533cfbf20cecd989950f7063a7664332b954df248707145055a9e48b1091

9c39605b1d05e69e5a10833b55a17e93494638fd69c4543745f0e0e90c3ba8dd

8e2e9040a08a54eb2600701e50e4137fd9959873e23cb5c6c4845e0a4f3f6564

51250a38ca79033e87c8efb39ecdc1e4551954047775212033dae8a2e37a976b

ebec96402f0d9c006351908cb3fda76c72869742a7de5ac923baec333ef089d3

8918d298d3b11a2c3dbb65bc1e88d7d0cc130a7aadfcfb13070bf18e5023ab86

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

Campaign

RLMA-2025-042552025-07-set7RLUA-2026-00753

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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