Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @gartnerx/gx-npm-messenger-util

Malware was discovered in the npm package @gartnerx/gx-npm-messenger-util. 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
  • @gartnerx/gx-npm-messenger-util

A critical malware incident was identified in the npm package @gartnerx/gx-npm-messenger-util. According to the GitHub Advisory (GHSA-9vfc-98mc-g3p5), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package installation, as the attacker may have gained full control of the system.\n\nThis represents a supply chain compromise through a malicious package distribution in the npm ecosystem.

Indicators of compromise

Packages
  • @gartnerx/gx-npm-messenger-util

Remediation

  • Immediately rotate all secrets and keys from a different, uncompromised computer
  • Remove the @gartnerx/gx-npm-messenger-util package from all affected systems
  • Conduct a full security audit of any system that had this package installed
  • Monitor affected systems for signs of unauthorized access or persistence mechanisms
  • Review package dependencies to identify any other potentially compromised packages
  • Consider full system reimaging if the package was installed on critical infrastructure

Sources

  1. GitHub Advisory GHSA-9vfc-98mc-g3p5 · GitHub Advisory Database

Cite this entry

"Malware in @gartnerx/gx-npm-messenger-util." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-gartnerx-gx-npm-messenger-util-q7c23h

Suggest a correction

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

  1. containedcritical

    Malicious code in testingsmthb1g (npm)

    The npm package testingsmthb1g contains malicious code in its postinstall script that acts as an install-time dropper, downloading and executing a Windows binary payload and exfiltrating platform information. The attack includes sandbox escape capabilities for WSL/virtualized Linux environments.

    npmCompromised package
  2. resolvedcritical

    Malicious code in mutex-core (npm)

    The npm package mutex-core, published under a name resembling the popular async-mutex library, contained malicious code including a staged loader that decrypts and executes hidden payloads. The package included obfuscated code that conditionally triggers AES-256-GCM decryption and execution of encrypted binary content when specific conditions are met.

    npmCompromised package
  3. containedcritical

    Malicious code in tyepescript-cli (npm)

    tyepescript-cli, a typosquat of the legitimate typescript package on npm, contains malicious postinstall code that downloads and executes a Windows binary (main.exe) and beacons to an attacker-controlled server. The package uses XOR obfuscation to hide URLs, commands, and IP addresses, with special logic to target both Windows and WSL environments.

    npmTyposquattingCompromised package
  4. containedcritical

    Malicious code in commandor-cli (npm)

    commandor-cli@1.0.0 on npm contains malicious postinstall script that downloads and executes a binary from an attacker-controlled GitHub repository. The script also beacons installation metadata to a command-and-control server and includes a PowerShell bridge to extend execution to Windows hosts on WSL systems.

    npmCompromised packageMalicious commit