MAL-2026-17200 Malicious code in aseity (PyPI)

Malicious package Published
Package
aseity
Registry
PyPI

What is MAL-2026-17200?

MAL-2026-17200 is a malicious package in aseity, published on 27 Sep 2026.

Official description

setup.py invokes aseity.compat._ensure_compat, which base64+zlib-decodes the DATA constant shipped in aseity/_shimdata.py and passes the resulting Python source to exec(), so the payload runs automatically on pip install. aseity/init.py runs the same routine, so a bare import aseity also triggers it. The decoded stage-1 performs VM and debugger checks, downloads https://thisisafalsepositive.st/cdn/v2/9f4e7a2c1b8d.png (a PNG carrying a ZIP inside its chunks), extracts a bundled python.exe and AppHost/main.py to a temp directory, and launches subprocess.Popen([py, entry, '-u', _USER, '–env', 'EXE', '–tag', 'PyPi']) with Windows creationflags DETACHED_PROCESS | CREATE_NO_WINDOW (0x00000008 | 0x08000000). A hardcoded per-victim UUID (_USER='e00db386-ab62-4dc1-91fd-21ef9ff3e6ef') is passed to the second stage. The domain thisisafalsepositive.st is not associated with any declared publisher, the delivered bytes are opaque, the payload is hidden as an encoded blob in a data-named module, and the launcher deliberately detaches with no visible window — the shape of a supply-chain dropper deploying a persistent second-stage implant on the installer's host.

During installation, obfuscated code is used to fetch code hidden in an image containing a Python application with a native extension module. This module holds an obfuscated infostealer which collects sensitive data and exfiltrates them to a C2 server retrieved from transaction history in the Polygon blockchain.


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

Campaign: 2026-09-donutautosellsrc

Reasons (based on the campaign):

  • infostealer

  • Downloads and executes a remote executable.

  • obfuscation

  • malware

  • native-extension

  • steganography

  • c2-in-blockchain

  • The package contains code to detect if it is running in a sandbox environment.

What should I do about MAL-2026-17200?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

Sources

Is MAL-2026-17200 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free