Which versions of ansishade are malicious?

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

How do I remediate ansishade if I installed it?

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

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

Yes — ansishade is associated with the 2024-11-tingetone 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 ansishade 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 ansishade (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 ansishade across your stack and pipelines.

Malicious package

ansishadePyPI

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

MAL-2024-12190

Immediate action

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

pip uninstall ansishade

What this malware does

Importing the module starts the banner() function, which downloads and runs an obfuscated remote script. The package seems to be a clone a one of existing similar packages.

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

Campaign: 2024-11-tingetone

Reasons (based on the campaign):

clones-real-package
obfuscation
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

f10534323fb0b043800273accc6b129e209d19f2ab97136ca2ac7b56b26492a8

c34f34cc1bdc60a4851d462f058187107a8c200d06ce08295d773f351fa1749a

896f00229ff836350c9bf8ee343c7e51cd0f9617339f8f69965153037ee8834a

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 ansishade (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 ansishade across your stack and pipelines.
If you installed it — respond
ansishade 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 ansishade 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 ansishade 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. ansishade 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

2024-11-tingetone

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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