Which versions of aseitylab are malicious?

The following PyPI versions of aseitylab are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate aseitylab if I installed it?

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

I already installed aseitylab — how do I know if it already compromised me?

If aseitylab 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.

Is aseitylab part of a known attack campaign?

Yes — aseitylab is associated with the 2026-09-donutautosellsrc, IN-MAL-2026-020624 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find aseitylab across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aseitylab (2 malicious versions).

Part of a larger attack: 2026-09-donutautosellsrc published 9 malicious packages. See the full campaign →

Malicious package

aseitylabPyPI

Advisory published Sep 28, 2026Updated Oct 25, 2026

aseitylab is a confirmed malicious PyPI package (MAL-2026-17240) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aseitylab (PyPI)

MAL-2026-17240

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall aseitylab

What this malware does

aseitylab/_shimdata.py contains a large base85-encoded, zlib-compressed blob stored as DATA. aseitylab/compat.py defines _ensure_compat(), which base85-decodes and zlib-inflates DATA and passes the result to exec(compile(..., '<aseitylab-compat>', 'exec')). setup.py imports aseitylab.compat and invokes _ensure_compat() during package build/install, and aseitylab/init.py calls the same function on every import, so the decoded payload runs both when the package is installed and whenever it is imported. Execution is gated by environment variables (ASEITYLAB_COMPAT=0, DAS_STAGED=1) that allow the payload to be suppressed in build or test environments. The README advertises a pure-Python task-orchestration toolkit with no runtime dependencies, which does not require a compressed, encoded executable blob shipped as 'compatibility shim data'. MANIFEST.in additionally excludes file names (loader_payload.py, make_armed.py, armed.json, manifest.benign.json) consistent with a build harness that produces separate 'armed' and 'benign' tarballs. The contents of the executed payload are not inspectable from the shipped source; installing or importing the package hands arbitrary code execution to whatever DATA decodes to.

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
The package contains code to detect if it is running in a sandbox environment.
malware
native-extension
steganography
c2-in-blockchain

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

24b99c2059065cbe44f7dac2f1d2878b237c58150c0890baa1856852e76fcb24

9b47f0f7a0776cad3d4c83604d35a0023a250d2f035e58129233095aa2b110a3

7a9abd6aaf665ceab13368a8983572e4df9a895f45b0fee615c2d2a1e82bd0f8

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for aseitylab (2 malicious versions).
If you installed it — respond
aseitylab 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.
Did it already run?
If aseitylab 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. aseitylab on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-donutautosellsrcIN-MAL-2026-020624

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database