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

fairsequencePyPI

Advisory published Updated

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

Malicious code in fairsequence (PyPI)

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

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 'fairsequence' @ 91.6 (pypi) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
91.6

Indicators of compromise (SHA-256)

929ae74bf14cceb38d619c97c2cf7b9d0316d0a9537b04f2f3b3c7e84b7b9683
b03620905754b702c5d4dff25571e4a8c9046d79927fbccc59d9f42c772b7a5a
f1230e40416399a228274fe18913e80c3e1fa3904ea4c040cb8c9e68b8d2752c
f00ff401545738adaa18b7e010454b44aed6a04f2846fa833f160d414d9146a2

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for fairsequence (version 91.6).

  2. If you installed it — respond

    fairsequence 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 fairsequence 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. fairsequence on PyPI has been identified as a malicious package (version 91.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 fairsequence-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

fairsequence (PyPI) malicious package — MAL-2024-10583 | O3 Security