Supply chain · pip · High

Malicious 'qoeoe' (PyPI) Package Exfiltrates Files, Poses Supply Chain Risk

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

A malicious package named 'qoeoe' (version 0.1.0) on PyPI has been identified as containing code designed to exfiltrate files to a remote location. This poses a critical supply chain risk, particularly for environments where this package might be integrated into Android-targeted projects.

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

What happened — Credential / secret theft

The 'qoeoe' package (version 0.1.0) on the PyPI registry contains hidden malicious code. This code is designed to exfiltrate files from the system where it is executed to an attacker-controlled remote location. The malicious functionality is concealed within the package's provided features.

How the attack works

This is a software supply chain attack where a seemingly legitimate or benign package is compromised with malicious functionality. When the package is installed and its code executed, the hidden malicious component activates, performing unauthorized actions such as data exfiltration. The attack leverages trust in package registries and automated dependency resolution.

Who's exposed

Profiles most at risk

  • Development teams using the PyPI ecosystem, especially those building or testing Android applications.
  • CI/CD pipelines that automatically pull and install dependencies from PyPI.
  • Organizations with internal package mirrors that have synchronized 'qoeoe' version 0.1.0.

Conditions that increase exposure

  • Projects with unpinned dependencies that could inadvertently pull the malicious 'qoeoe' version 0.1.0.
  • Lack of dependency lockfiles (e.g., `requirements.txt` with exact versions) that prevent non-deterministic builds.
  • Environments where packages are installed with elevated privileges, increasing the potential impact of file exfiltration.
  • Systems or projects specifically targeting Android, as the advisory indicates a 'target:android' characteristic.

Blast-radius scenarios

  • An attacker could gain unauthorized access to sensitive files and data from development machines or build servers.
  • Compromised build environments could lead to further supply chain attacks if malicious code is injected into downstream artifacts.
  • Intellectual property or confidential project files could be exfiltrated, leading to data breaches or competitive disadvantages.

What to do (defensive)

Detect

  • Scan existing project dependencies for 'qoeoe' version 0.1.0 using dependency analysis tools.
  • Monitor network traffic for unusual outbound connections from build systems or development environments that might indicate data exfiltration.
  • Implement file integrity monitoring (FIM) on critical system directories to detect unauthorized file access or modification.

Contain

  • Immediately remove 'qoeoe' version 0.1.0 from all project dependencies and lockfiles.
  • Isolate any systems or environments where 'qoeoe' version 0.1.0 was installed or executed.
  • Block network access to known malicious domains or IP addresses associated with data exfiltration, if available.

Remediate

  • Audit all systems that installed 'qoeoe' version 0.1.0 for signs of compromise, including unauthorized file access or modification.
  • Rotate any credentials or API keys that were present on compromised systems during the package's execution.
  • Update dependency management practices to use strict version pinning and lockfiles to prevent similar incidents in the future.
  • Consider implementing a software supply chain security solution that scans packages for known vulnerabilities and malicious content before integration.

Frontier verdict — High

Prioritize immediate removal of 'qoeoe' version 0.1.0 from all PyPI projects due to critical file exfiltration risk, especially for Android-targeted applications.

Sources

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