Which versions of k7eeel are malicious?

The following PyPI versions of k7eeel are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate k7eeel if I installed it?

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

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

Yes — k7eeel is associated with the RLMA-2025-04780, 2025-08-k7eel, RLUA-2026-00447 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 k7eeel 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 k7eeel (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging k7eeel across your stack and pipelines.

Malicious package

k7eeelPyPI

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

MAL-2025-47776

Immediate action

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

pip uninstall k7eeel

What this malware does

Importing the module downloads and executes widely recognized malware

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

Campaign: 2025-08-k7eel

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

90b6e2c0e230c8792ef937579dc78ea62db1db7bc55f68009b51c6180762a6e8

b4d8d5066f90f62ad5ffcd646fb5cf9c1e0a6d982ff6d4bd79accddc4fd61155

2efb19cb81393cb377946edce80dfdae18968a190f7ab3a35dae3109ff17026c

f5034dce8cee23c4b95f922df8d7ac8d3700220f2c94549be0fb33b5f20506d9

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

Campaign

RLMA-2025-047802025-08-k7eelRLUA-2026-00447

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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