Supply chain · npm · High

Malicious npm package 'gear-composer' (v1.0.126) identified in credential theft campaign

Threat Engine Auto-Feed · data current as of 2026-08-19

The npm package 'gear-composer' version 1.0.126 contains malicious code designed for credential harvesting and exfiltration. It operates via an install-time agent, scanning for secrets, and relaying collected data to external services like Discord and HuggingFace. Organizations using this specific version are at high risk of sensitive data exposure.

  • Package: npm / gear-composer
  • Affected versions: = 1.0.126
  • Severity: critical
  • Reach: ~0/wk
  • Exposure: 60/100 (High)

What happened — Credential / secret theft

The npm package 'gear-composer' version 1.0.126 has been identified as malicious. It includes components that form an install-time credential harvest and exfiltration pipeline. This involves a post-install script that performs host identification and initiates outbound network activity, along with modules designed to scan for and exfiltrate secrets.

How the attack works

This attack leverages a malicious software package installed as a dependency. Upon installation, a post-install script is triggered, which then executes an agent. This agent scans the host's filesystem for sensitive information, such as credentials, which are often obfuscated. The collected data is then exfiltrated to attacker-controlled endpoints using various network operations, potentially via hardcoded relay destinations.

Who's exposed

Profiles most at risk

  • Development teams using npm for package management
  • CI/CD pipelines that pull dependencies without strict version pinning
  • Organizations with build systems that install 'gear-composer' v1.0.126

Conditions that increase exposure

  • Direct or transitive dependency on 'gear-composer' version 1.0.126
  • Lack of package lockfiles or unpinned dependency versions allowing the malicious version to be installed
  • Build environments with broad network egress permissions
  • Internal package mirrors that have synchronized the malicious version

Blast-radius scenarios

  • An attacker could gain access to sensitive credentials (e.g., API keys, tokens) present in the build environment or source code.
  • Compromised credentials could lead to unauthorized access to internal systems, cloud resources, or third-party services.
  • The exfiltration of host identification data could aid in further targeted attacks against the affected environment.

What to do (defensive)

Detect

  • Scan dependency trees for 'gear-composer' version 1.0.126.
  • Monitor network traffic from build environments for suspicious outbound connections to Discord, HuggingFace, or other unknown external endpoints.
  • Review post-install scripts and package contents for unusual or obfuscated code, especially those performing file system scans or network activity.

Contain

  • Immediately quarantine any systems or build environments found to have installed 'gear-composer' version 1.0.126.
  • Block network egress from build environments to known malicious exfiltration domains (e.g., specific Discord or HuggingFace endpoints identified in the advisory).
  • Revoke and rotate any credentials that may have been exposed on compromised systems.

Remediate

  • Remove 'gear-composer' version 1.0.126 from all projects and package caches.
  • Update package lockfiles to explicitly pin known-good versions of all dependencies.
  • Implement strict dependency versioning and review processes for new package introductions.
  • Conduct a thorough forensic analysis of any systems where the malicious package was installed to identify the scope of compromise and ensure complete removal.

Frontier verdict — High

Prioritize immediate detection and removal of 'gear-composer' v1.0.126 due to its critical severity and credential theft capabilities.

Sources

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