Which versions of k7eel2-ss are malicious?

The following PyPI versions of k7eel2-ss are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate k7eel2-ss if I installed it?

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

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

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

Malicious package

k7eel2-ssPyPI

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

MAL-2025-41421

Immediate action

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

pip uninstall k7eel2-ss

What this malware does

The package downloads and executes an executable from a hardcoded URL. The executable is classifed as Trojan and confirmed by 47 top sources. The package downloads malware from https://github.com/deprosinal/legendary-funicular github repo, namely helo.exe

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.1

Indicators of compromise (SHA-256)

81ee2d9f5186aee9287ffeb1a13489caa1684392d3c7d37cf33465c9e2e6ea0a

ad3813336ff34d8c396fb18c6190c9dab055ad08f3624819fe53d710d1b84ef1

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

Campaign

2025-08-k7eel

References

Credits

Kamil Mańkowski (kam193)
SafeDep · finder

Detect & block this

O3 blocks k7eel2-ss-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