Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in sui-gql-core

Malware was discovered in the npm package sui-gql-core. Systems with this package installed or running are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with sui-gql-core installed or running
Ecosystems
Attack vectors
Affected entities
  • sui-gql-core

The npm package sui-gql-core was found to contain malware. According to the GitHub advisory, any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the malicious 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 compromise.\n\nThis is a critical supply chain incident affecting the npm ecosystem.

Indicators of compromise

Packages
  • sui-gql-core

Remediation

  • Immediately isolate any system with sui-gql-core installed or running from the network
  • Rotate all secrets, API keys, and credentials stored on affected systems from a different, uncompromised computer
  • Remove the sui-gql-core package from all affected systems
  • Perform a full security audit and malware scan of affected systems
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider the affected system(s) potentially compromised and plan for full rebuild if critical infrastructure

Sources

  1. GitHub Advisory GHSA-rg66-wjvq-h8xm · GitHub Advisory Database

Cite this entry

"Malware in sui-gql-core." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 17, 2026; last updated August 17, 2026. https://supplychainattack.org/incident/malware-in-sui-gql-core-fl48nn

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 pump-segments-sdk (npm)

    The npm package pump-segments-sdk contained malicious code in a postinstall hook that exfiltrated sensitive system and npm configuration data to an attacker-controlled server. The package collected hostname, environment variables, system information, npm auth tokens, and attempted to read password hashes.

    npmCompromised package
  2. containedcritical

    Malicious code in ts-rand-sdk (npm)

    The npm package ts-rand-sdk contained malicious code disguised as a product catalog loader. When the advertised getTransactions() API was called, hidden obfuscated JavaScript was decoded and executed with full Node.js capabilities, enabling arbitrary filesystem, process, and network access on affected systems.

    npmCompromised package
  3. resolvedcritical

    Malicious code in lodsh-cli (npm)

    lodsh-cli, a typosquat of lodash-cli on npm, contained malicious code in its postinstall script that executed arbitrary remote code and exfiltrated system information. The package downloaded a Windows executable and sent platform data to a hardcoded IP address.

    npmTyposquattingCompromised package
  4. containedcritical

    Malicious code in lodahsjs (npm)

    The npm package lodahsjs is a typosquatting attack on 'lodash' that contains malicious code in its postinstall script. Upon installation, it exfiltrates system information to a C2 server and downloads and executes a Windows binary, with capability to bridge WSL environments to compromise the host Windows system.

    npmCompromised packageTyposquatting