Supply chain · pip · High

Malicious 'web3-eth-account' (pip) Poses Critical Supply Chain Risk

Threat Engine Auto-Feed · data current as of 2026-09-11

A malicious typosquatting package, 'web3-eth-account' version 0.14.0, has been identified in the pip ecosystem. This package is a clone of a legitimate library and contains import-time malicious code that activates under specific environmental conditions. If activated, it downloads and executes a remote payload, posing a critical supply chain threat.

  • Package: pip / web3-eth-account
  • Affected versions: = 0.14.0
  • Severity: critical
  • Reach: unknown
  • Exposure: 65/100 (High)

What happened — Typosquatting

The 'web3-eth-account' package (version 0.14.0) in the pip ecosystem was found to contain malicious code. This package is a typosquatting clone of a legitimate library. Its malicious functionality activates during import if specific environment variables are set. Upon activation, it queries the blockchain to retrieve a URL for a next-stage payload, which is then downloaded and executed.

How the attack works

This attack leverages typosquatting, where a malicious package mimics a legitimate one to trick users into installing it. The malicious code is designed to activate conditionally, likely to evade detection. Once activated, it establishes a command-and-control (C2) channel by querying a blockchain smart contract for a payload URL. This allows the attacker to dynamically deliver and execute arbitrary code on compromised systems, bypassing static analysis.

Who's exposed

Profiles most at risk

  • Development teams using the pip ecosystem, especially those working with blockchain-related libraries.
  • CI/CD pipelines configured to pull the latest unpinned versions of dependencies.
  • Organizations with developers who might mistype package names during installation.

Conditions that increase exposure

  • Unpinned dependencies in project manifests (e.g., requirements.txt without specific versions).
  • Lack of lockfiles (e.g., poetry.lock, pipenv.lock) to ensure deterministic builds.
  • Use of internal package mirrors that do not vet packages for known malicious content.
  • Environments where specific attacker-controlled environment variables are present.

Blast-radius scenarios

  • If installed and activated, an attacker can achieve remote code execution on the system where the package is run.
  • The blast radius extends to any system that builds or runs software dependent on this specific malicious package version, potentially leading to data exfiltration, further system compromise, or lateral movement within the network.

What to do (defensive)

Detect

  • Scan dependency trees for 'web3-eth-account' version 0.14.0.
  • Monitor network traffic for unusual outbound connections from build systems or applications, especially to blockchain networks or unknown URLs.
  • Implement software composition analysis (SCA) tools to identify known malicious packages and typosquats.
  • Review environment variables in build and runtime environments for suspicious configurations that could activate dormant malicious code.

Contain

  • Immediately quarantine or isolate any systems identified as having installed 'web3-eth-account' version 0.14.0.
  • Block network access to known C2 infrastructure or suspicious blockchain query endpoints from affected systems.
  • Temporarily halt builds that might pull new dependencies until a review of package sources and pinning strategies is complete.

Remediate

  • Remove 'web3-eth-account' version 0.14.0 from all project dependencies.
  • Replace the malicious package with the legitimate counterpart, ensuring correct spelling and version pinning.
  • Force-rebuild all affected applications and services with verified, clean dependencies.
  • Rotate credentials and API keys that might have been exposed on compromised systems.
  • Educate developers on typosquatting risks and the importance of verifying package names and sources.

Frontier verdict — High

Prioritize immediate detection and removal of 'web3-eth-account' version 0.14.0 due to its critical severity and remote code execution capabilities via blockchain-based C2.

Sources

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