Supply chain · pip · High

CRITICAL: Malicious 'proxy-rubikis' (PyPI) package exfiltrates files

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

A critical malicious package, 'proxy-rubikis' version 0.1.0, has been identified in the PyPI ecosystem. This package is designed for automated file exfiltration, posing a significant risk of credential and secret theft to any system where it is installed. Organizations using Python dependencies should immediately check for its presence.

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

What happened — Credential / secret theft

The 'proxy-rubikis' package, specifically version 0.1.0, was found to contain malicious code. This code is designed to automatically exfiltrate files from the system where the package is installed. The advisory categorizes this as a clearly malicious campaign with infostealer intent.

How the attack works

This attack leverages a malicious software package to compromise a system. Once installed, the package executes code that identifies and extracts sensitive files, then transmits them to an attacker-controlled destination. This type of supply-chain attack exploits trust in public package repositories to deliver harmful payloads.

Who's exposed

Profiles most at risk

  • Development teams using Python (PyPI) dependencies
  • CI/CD pipelines that pull Python packages
  • Organizations with Android development environments, as it targets Android
  • Any system or application that directly or indirectly depends on 'proxy-rubikis' version 0.1.0

Conditions that increase exposure

  • Unpinned dependencies that allow fetching the latest (malicious) version
  • Lack of dependency lockfiles (e.g., requirements.txt with exact versions, poetry.lock)
  • Use of internal package mirrors that have not been updated to exclude the malicious package
  • Automated build processes that do not vet new package versions

Blast-radius scenarios

  • An attacker could gain unauthorized access to sensitive files, including credentials, configuration files, and proprietary code.
  • Compromised systems could lead to further network penetration or data breaches.
  • The exfiltration of files could result in intellectual property theft or regulatory non-compliance.

What to do (defensive)

Detect

  • Scan all Python project dependencies for 'proxy-rubikis' version 0.1.0.
  • Review build logs and dependency trees for any unexpected package installations.
  • Monitor network traffic for unusual outbound connections from development or build environments, especially those involving file transfers.

Contain

  • Immediately quarantine or isolate any systems found to have 'proxy-rubikis' version 0.1.0 installed.
  • Block 'proxy-rubikis' version 0.1.0 at your package registry or proxy level.
  • Revoke and rotate any credentials that may have been present on compromised systems.

Remediate

  • Remove 'proxy-rubikis' version 0.1.0 from all affected environments and projects.
  • Rebuild affected applications and systems from trusted sources, ensuring all dependencies are verified.
  • Implement strict dependency pinning and use lockfiles to prevent automatic updates to potentially malicious versions.
  • Enhance supply chain security practices, including dependency auditing and integrity checks.

Frontier verdict — High

Prioritize immediate detection and removal of 'proxy-rubikis' version 0.1.0 due to critical file exfiltration capabilities.

Sources

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