NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: 2024-11-byted-dast published 183 malicious packages. See the full campaign →
Malicious package

tarseirPyPI

Advisory published Updated

tarseir is a confirmed malicious PyPI package (MAL-2024-10462) that steals credentials and exfiltrates sensitive data (malicious version 912.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tarseir (PyPI)

MAL-2024-10462
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall tarseir

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

  • The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

  • typosquatting

  • dependency-confusion

The OpenSSF Package Analysis project identified 'tarseir' @ 912.6 (pypi) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
912.6

Indicators of compromise (SHA-256)

bde59205ef4ee15d8744f0efe772084f90f8adaf50e577decd99d83a93e58af2
37cbc995a19904b2470a5b1bd7d1d1c5aaf2e6ad829f895b591ffcab593a25b5
fb4497700ac14b8516caa9617140ab894fba22e92b91a7812d576b581ab7cc85
744bc819f2b9e322ac04a1b3444a0cb5106aa0686ea5668d4e8e1e37f2b30474

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for tarseir (version 912.6).

  2. If you installed it — respond

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

  3. Did it already run?

    If tarseir 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. tarseir on PyPI has been identified as a malicious package (version 912.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-11-byted-dast

References

Credits

  • Kamil Mańkowski (kam193)
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks tarseir-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

tarseir (PyPI) malicious package — MAL-2024-10462 | O3 Security