Supply chain · npm · High

Critical npm Package Compromise: @antv/g-plugin-dom-interaction Steals Credentials

Threat Engine Auto-Feed · data current as of 2026-07-26

The npm package `@antv/g-plugin-dom-interaction` version 2.2.31 contains malicious code as part of the 'Mini Shai-Hulud' supply chain attack. This compromise aims to steal various credentials and establish persistence, posing a critical risk to development environments and CI/CD pipelines.

  • Package: npm / @antv/g-plugin-dom-interaction
  • Affected versions: = 2.2.31
  • Severity: critical
  • Reach: unknown
  • Exposure: 65/100 (High)

What happened — Credential / secret theft

The npm package `@antv/g-plugin-dom-interaction` version 2.2.31 was compromised as part of the 'Mini Shai-Hulud' campaign. A threat actor gained control of an npm account and published malicious versions across numerous packages, including this one. The malicious version injects a `preinstall` hook that executes an obfuscated Bun script designed to exfiltrate sensitive data.

How the attack works

This is a supply chain attack where a legitimate package was modified to include malicious code. When the compromised package is installed, a `preinstall` script is triggered. This script executes a payload that collects various credentials and secrets from the environment. The stolen data is then exfiltrated to attacker-controlled infrastructure, and mechanisms are put in place to maintain persistence within the compromised system, including CI/CD workflow injection and system daemons.

Who's exposed

Profiles most at risk

  • Development teams using the npm ecosystem
  • Organizations with CI/CD pipelines that automatically pull package dependencies
  • Developers or systems that have installed `@antv/g-plugin-dom-interaction` version 2.2.31

Conditions that increase exposure

  • Unpinned dependencies that allow automatic updates to vulnerable versions
  • Lack of lockfiles (e.g., `package-lock.json`) to ensure consistent dependency versions
  • Use of internal package mirrors that may not have updated advisories or block malicious versions
  • Environments where sensitive credentials (e.g., AWS keys, GitHub PATs, npm tokens) are accessible during package installation

Blast-radius scenarios

  • An attacker gains access to sensitive credentials (AWS keys, GitHub PATs, npm tokens, GCP service accounts, Azure credentials, Kubernetes tokens, SSH keys, Docker auth configs, database connection strings, Stripe keys, Slack tokens).
  • Persistence is established within development environments or CI/CD systems via injected GitHub Actions workflows or system daemons.
  • The compromised system becomes a platform for further attacks, potentially leading to broader organizational compromise or data breaches.

What to do (defensive)

Detect

  • Scan `package-lock.json` or `yarn.lock` files for `@antv/g-plugin-dom-interaction` version 2.2.31.
  • Monitor network traffic for unusual outbound connections from build systems or developer machines, especially to GitHub API endpoints not associated with legitimate operations.
  • Review CI/CD logs for unexpected script execution during package installation or new, unauthorized workflow definitions (e.g., `Run Copilot`).
  • Check for the presence of unusual system daemons or scheduled tasks (e.g., `kitty-monitor`).

Contain

  • Immediately quarantine any systems or CI/CD runners found to have installed `@antv/g-plugin-dom-interaction` version 2.2.31.
  • Block network access for compromised systems to prevent further exfiltration.
  • Revoke and rotate all credentials (AWS keys, GitHub PATs, npm tokens, etc.) that were present on affected systems during the compromise period.
  • Prevent further installations of the specific malicious version by configuring package registries or firewalls.

Remediate

  • Remove `@antv/g-plugin-dom-interaction` version 2.2.31 from all projects and ensure a safe, known-good version is used, or consider an alternative package.
  • Rebuild affected systems from trusted images, ensuring all dependencies are verified and free of malicious code.
  • Implement strict dependency pinning using lockfiles (`package-lock.json`, `yarn.lock`) and review them regularly.
  • Enhance CI/CD security by implementing least privilege for build processes and regularly auditing workflow definitions for unauthorized changes.

Frontier verdict — High

Prioritize immediate detection and remediation for `@antv/g-plugin-dom-interaction` version 2.2.31 due to critical credential theft and persistence capabilities.

Sources

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