ZDF
Sign inSign up

Vulnerabilities

Security incident · MAL-2026-17200

Malicious code in aseity (PyPI)

Published Sep 27, 2026 · catalog updated Oct 25, 2026 · Malicious code in aseity

Last checked Oct 26, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for MAL-2026-17200. A missing EPSS score is not a low risk. Compare Malicious code in aseity with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Malicious code in aseity).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Not established
Affected products
PyPI aseity

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d65d0df302f9fdd618d08a8bc095702f5b6594712ba82205c758c710fee9006e) 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 . aseity/__init__.py runs the same routine, so a bare 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. ## Source: kam193 (cf65ea5c0fe1eeef9f47a75d65e291a715094076714694247ad03714eabc53ca) 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

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • PyPI aseity0.1.0

How to fix MAL-2026-17200

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for MAL-2026-17200. A missing EPSS score is not a low risk. Compare Malicious code in aseity with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0.1.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 27, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d65d0df302f9fdd618d08a8bc095702f5b6594712ba82205c758c710fee9006e) 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 . aseity/__init__.py runs the same r

  2. Oct 25, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d65d0df302f9fdd618d08a8bc095702f5b6594712ba82205c758c710fee9006e) 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 . aseity/__init__.py runs the same r

Sources

References

Freshness

Last verified in this catalog Oct 25, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • PyPA Advisory DatabaseOct 26, 2026
  • OpenSSF OSV / OSV ScannerOct 26, 2026