Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @bapiweb-ux/bapi-header

Malware was discovered in the npm package @bapiweb-ux/bapi-header. Systems with this package installed are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • @bapiweb-ux/bapi-header

A critical malware incident was identified in the npm package @bapiweb-ux/bapi-header, published via GitHub Advisory GHSA-q8qh-2q32-qvc7 on June 29, 2026.\n\nAny computer with this package installed or running should be considered fully compromised. The malware grants outside entities full control of affected systems, potentially allowing exfiltration of secrets, keys, and other sensitive data.\n\nImmediate remediation requires rotating all secrets and keys from a separate, uncompromised computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise achieved.\n\nOrganizations should audit their dependency trees to identify all systems that may have installed this package and take appropriate containment and recovery measures.

Indicators of compromise

Packages
  • @bapiweb-ux/bapi-header

Remediation

  • Identify all systems with @bapiweb-ux/bapi-header installed
  • Isolate affected systems from the network immediately
  • Rotate all secrets, API keys, and credentials from a separate, uncompromised computer
  • Remove the package from all affected systems
  • Conduct forensic analysis to identify any additional malicious software installed
  • Review system logs and network traffic for signs of data exfiltration or lateral movement
  • Restore systems from clean backups if available, or rebuild from scratch

Sources

  1. GitHub Advisory GHSA-q8qh-2q32-qvc7 · GitHub Advisory Database

Cite this entry

"Malware in @bapiweb-ux/bapi-header." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-bapiweb-ux-bapi-header-12ahb4

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. resolvedcritical

    Malicious code in typescirpt-cli (npm)

    The npm package typescirpt-cli (a typosquat of typescript-cli) contained malicious code in its postinstall script that downloads and executes a binary (main.exe) on Windows and WSL systems, and exfiltrates system metadata to a hardcoded IP address.

    npmTyposquattingCompromised package
  2. containedcritical

    Malicious code in typescipt-core (npm)

    The npm package typescipt-core (a typosquat of typescript) contained malicious postinstall code that downloads and executes a second-stage payload on Windows and WSL systems. The dropper exfiltrates host profile information to 193.70.34.101:20099 before fetching attacker-controlled executables.

    npmCompromised packageTyposquatting
  3. containedcritical

    Malicious code in typesript-cli (npm)

    The npm package 'typesript-cli' (a one-character typosquat of 'typescript') contains malicious code in its postinstall script that downloads and executes a Windows PE binary, and can cross the Linux/WSL sandbox boundary to execute payloads on the Windows host. The script also beacons to a hardcoded IP endpoint.

    npmTyposquattingCompromised package
  4. resolvedcritical

    Malicious code in @mohamed_nowisar/depconf-canary-test (npm)

    The npm package @mohamed_nowisar/depconf-canary-test contained malicious code in its preinstall hook that automatically collected and exfiltrated host and CI environment information to an attacker-controlled webhook endpoint without user consent.

    npmCompromised package