Supply chain · pip · High

Critical: Malicious 'aseity' package in PyPI performs credential theft

Threat Engine Auto-Feed · data current as of 2026-09-27

The 'aseity' package (version 0.1.0) in the PyPI ecosystem contains obfuscated malicious code designed to steal sensitive data. During installation, it fetches and executes an infostealer that exfiltrates collected information to a C2 server, posing a critical supply-chain risk.

  • Package: pip / aseity
  • Affected versions: = 0.1.0
  • Severity: critical
  • Reach: unknown
  • Exposure: 65/100 (High)

What happened — Credential / secret theft

The 'aseity' package (version 0.1.0) on PyPI was identified as malicious. During its installation process, it employs obfuscated code to retrieve and execute a hidden Python application containing a native extension module. This module functions as an infostealer, collecting sensitive data and transmitting it to a command-and-control (C2) server whose address is concealed within the Polygon blockchain's transaction history.

How the attack works

This attack leverages steganography and obfuscation to conceal a data-stealing payload. The malicious package, upon installation, initiates a multi-stage process: it first decrypts or decodes hidden code, which then fetches a secondary payload (an infostealer) from an unconventional source (an image file). This infostealer then collects sensitive information from the compromised system and transmits it to an external server, with the C2 address itself hidden within blockchain transaction data to evade detection. The package also includes sandbox detection capabilities.

Who's exposed

Profiles most at risk

  • Any development or production environments that installed 'aseity' version 0.1.0 from PyPI
  • Organizations with CI/CD pipelines that automatically pull the latest versions of dependencies
  • Teams whose build processes do not validate package integrity or source

Conditions that increase exposure

  • Direct or transitive dependency on 'aseity' version 0.1.0
  • Lack of pinned dependencies or use of broad version ranges in `requirements.txt` or `pyproject.toml`
  • Absence of package integrity checks (e.g., hash verification) during installation
  • Environments with network access to external resources during package installation

Blast-radius scenarios

  • An attacker could gain access to sensitive data, including credentials, API keys, and other proprietary information from compromised systems.
  • The exfiltration of data to an external C2 server could lead to further compromise of internal systems or data breaches.
  • Compromised systems could be used as a pivot point for lateral movement within the network.

What to do (defensive)

Detect

  • Scan `requirements.txt` and `pyproject.toml` files for direct or transitive dependencies on 'aseity' version 0.1.0.
  • Monitor network traffic for unusual outbound connections from build environments or production systems to unknown IP addresses or domains, especially those associated with cryptocurrency blockchains.
  • Implement file integrity monitoring for Python package directories to detect unauthorized modifications or additions.
  • Review system logs for suspicious process execution during package installation.

Contain

  • Immediately isolate any systems or environments found to have installed 'aseity' version 0.1.0.
  • Block network communication to known C2 infrastructure or suspicious external IP addresses from affected systems.
  • Revoke and rotate any credentials, API keys, or secrets that may have been present on compromised systems.
  • Prevent further installations of 'aseity' version 0.1.0 by configuring package managers to block it or by using private package indexes.

Remediate

  • Remove 'aseity' version 0.1.0 from all affected environments and replace it with a known-good, verified alternative if functionality is required.
  • Perform a comprehensive security audit of all systems that installed the malicious package to identify any lingering compromise or backdoors.
  • Update dependency management practices to pin exact versions and use lock files to ensure deterministic builds.
  • Implement and enforce package integrity checks (e.g., using `pip install --require-hashes`) to verify the authenticity of downloaded packages.

Frontier verdict — High

Prioritize immediate detection and removal of 'aseity' version 0.1.0 due to its critical infostealer capabilities and credential theft risk.

Sources

For detection-engineering and awareness only · point-in-time · not security advice · sourced from the GitHub Advisory Database.