Supply chain · pip · High

Critical Malicious PyPI Package 'agent-vx' Poses Remote Code Execution Risk

Threat Engine Auto-Feed · data current as of 2026-10-10

The PyPI package 'agent-vx' version 0.1.0 contains malicious code that establishes persistence, exfiltrates files, and allows for remote code execution. This poses a critical supply-chain risk, enabling attackers to compromise systems where the package is installed.

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

What happened — Credential / secret theft

The 'agent-vx' package (PyPI) version 0.1.0 was identified as malicious. It installs a persistent job on the victim's machine, designed to exfiltrate files and execute remote commands.

How the attack works

This is a supply-chain attack where a malicious package is introduced into a public registry. When developers or automated systems install this package, the embedded malicious code executes, establishing persistence and enabling unauthorized data exfiltration and remote command execution on the compromised system.

Who's exposed

Profiles most at risk

  • Development teams using the PyPI ecosystem
  • Organizations with CI/CD pipelines that pull unpinned or latest versions of dependencies
  • Systems where 'agent-vx' version 0.1.0 was directly or transitively installed

Conditions that increase exposure

  • Unpinned dependencies in project manifests (e.g., requirements.txt without specific versions)
  • Lack of dependency lockfiles (e.g., poetry.lock, pip-tools generated files)
  • Use of internal package mirrors that do not vet upstream packages
  • Automated builds that install dependencies without integrity checks

Blast-radius scenarios

  • An attacker gains persistent access to a developer's workstation or a build server
  • Sensitive files and credentials are exfiltrated from compromised systems
  • Attackers execute arbitrary commands on systems running the malicious package, potentially leading to further network compromise or data breaches

What to do (defensive)

Detect

  • Scan dependency trees for 'agent-vx' version 0.1.0
  • Monitor network traffic for unusual outbound connections from systems that installed the package
  • Review system logs for newly created persistent jobs or suspicious process execution
  • Utilize software composition analysis (SCA) tools to identify known malicious packages

Contain

  • Immediately quarantine or isolate any systems identified with 'agent-vx' version 0.1.0
  • Block network communication from affected systems to external unknown IP addresses
  • Revoke and rotate any credentials or API keys that may have been present on compromised systems

Remediate

  • Remove 'agent-vx' version 0.1.0 from all affected environments and dependency lists
  • Rebuild affected systems from trusted images or known good states
  • Implement strict dependency version pinning and use lockfiles in all projects
  • Enhance software supply chain security practices, including package integrity checks and trusted registries

Frontier verdict — High

Prioritize immediate detection and removal of 'agent-vx' version 0.1.0 due to critical remote code execution and data exfiltration capabilities.

Sources

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