CTIPilot

Python (PyPI package ecosystem)

product · product:python-pypi-package-ecosystem single-source

Coverage timeline
1
first 2026-07-14 → last 2026-07-14
Peak priority
notable
1 notable
Sources cited
1
1 hosts
Sections touched
1
research
Co-occurring entities
1
see Co-occurring entities below
ATT&CK techniques
3
pinned v19.2 · see below

Hunting pivots

Releases covered
Python (PyPI package ecosystem)
ATT&CK techniques
T1059.006T1195.001T1574.007
Tags
supply-chain

ATT&CK techniques

3 techniques observed across 1 entry, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v19.2 · compare on the matrix · Navigator layer (JSON)

Initial Access TA0001

T1195.001Supply Chain Compromise: Compromise Software Dependencies and Development Tools×1

Adversaries may manipulate software dependencies and development tools prior to receipt by a final consumer for the purpose of data or system compromise. Applications often depend on external software to function properly. Popular open source projects that are used as dependencies in many applications, such as pip and NPM packages, may be targeted as a means to add malicious code to users of the dependency. This may also include abandoned packages, which in some cases could be re-registered by threat actors after being removed by adversaries. Adversaries may also employ "typosquatting" or name-confusion by choosing names similar to existing popular libraries or packages in order to deceive a user.

Evidence: 2026-07-14/talos-serpents-tongue-python-package-code-execution-taxonomy · ATT&CK page ↗

Execution TA0002

T1059.006Command and Scripting Interpreter: Python×1

Adversaries may abuse Python commands and scripts for execution. Python is a very popular scripting/programming language, with capabilities to perform many functions. Python can be executed interactively from the command-line (via the <code>python.exe</code> interpreter) or via scripts (.py) that can be written and distributed to different systems. Python code can also be compiled into binary executables.

Evidence: 2026-07-14/talos-serpents-tongue-python-package-code-execution-taxonomy · ATT&CK page ↗

T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable×1

Adversaries may execute their own malicious payloads by hijacking environment variables used to load libraries. The PATH environment variable contains a list of directories (User and System) that the OS searches sequentially through in search of the binary that was called from a script or the command line.

Evidence: 2026-07-14/talos-serpents-tongue-python-package-code-execution-taxonomy · ATT&CK page ↗

Stealth TA0005

T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable×1

Adversaries may execute their own malicious payloads by hijacking environment variables used to load libraries. The PATH environment variable contains a list of directories (User and System) that the OS searches sequentially through in search of the binary that was called from a script or the command line.

Evidence: 2026-07-14/talos-serpents-tongue-python-package-code-execution-taxonomy · ATT&CK page ↗

Story timeline

  1. 2026-07-14Cisco Talos maps the full taxonomy of Python-package build-time and import-time code execution ("The Serpent's Tongue")
    researchTalos catalogues where malicious Python packages execute code across the install lifecycle, including persistent .pth and site-hook footholds

Where this entity is cited

  • research1

Source distribution

  • blog.talosintelligence.com1 (100%)

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

All cited sources (1)

Entries about Python (PyPI package ecosystem) (1)

2026-07-14 · view entry permalink →

NOTABLENATOB2

Cisco Talos maps the full taxonomy of Python-package build-time and import-time code execution ("The Serpent's Tongue")

Cisco Talos published a comprehensive technical survey of code-execution paths across the Python packaging lifecycle, repository hosting (PyPI, version-control, custom servers), source (sdist) and wheel distribution formats, and installation into virtual or system-wide environments, split into two classes and assessed for persistence (Cisco Talos, 2026-07-14). Build-hook abuses fire code during installation: setup.py executes automatically on install or download, so a malicious command class runs arbitrary code as a transient one-shot. The more consequential class is persistence: a .pth path-configuration file dropped into site-packages is executed on every subsequent Python invocation, and site-hook modules (sitecustomize.py/usercustomize.py) and PYTHONPATH hijacking behave the same way, the payload survives well beyond install time. Talos ties the .pth technique directly to TeamPCP's supply-chain compromise of the litellm package and the import-time __init__.py payload to its lightning compromise, part of a documented run of TeamPCP supply-chain waves. The piece closes on defensive measures, dependency auditing (pip-audit), hashed lock files, install-time controls and a dependency-cooldown window before adopting newly-published versions.

executes automatically during installation or download, allowing for the execution of arbitrary code.

they are executed with every invocation of Python, therefore exhibiting a persistent behavior on the victim endpoint.

Cisco Talos 2026-07-14
research14 Jul 20:22Zsingle-sourceOpen finding ↗
Sources: Cisco Talos