Which versions of sankislayer are malicious?

The following PyPI versions of sankislayer are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate sankislayer if I installed it?

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

If sankislayer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is sankislayer part of a known attack campaign?

Yes — sankislayer is associated with the 2026-07-sankislayer 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 sankislayer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sankislayer (version 1.0.0).

Malicious package

sankislayerPyPI

Advisory published Jul 10, 2026Updated Jul 10, 2026

sankislayer is a confirmed malicious PyPI package (MAL-2026-10119) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sankislayer (PyPI)

MAL-2026-10119

Immediate action

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

pip uninstall sankislayer

What this malware does

Obfuscated code provides a Telegram bot to join a spamming botnet. Centrally controlled bots can be used to spam other Telegram channels (via looped posting, changing photos, or titles).

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

Campaign: 2026-07-sankislayer

Reasons (based on the campaign):

obfuscation
abusing-3rd-api
target:telegram

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

74a2d321c0a35b52bc8ba63b8c13dd8e883d63419ed8aa304b648d3599f98ad8

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for sankislayer (version 1.0.0).
If you installed it — respond
sankislayer 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 sankislayer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. sankislayer on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-07-sankislayer

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database