Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in index-ulid

The npm package index-ulid was found to contain malware, potentially giving attackers full control of affected systems. Any computer with this package installed or running should be considered fully compromised.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
npm
Attack vectors
Compromised package
Affected entities
  • index-ulid

The npm package index-ulid was identified as containing malware. According to the GitHub Advisory (GHSA-95pm-8vrw-2wrp), any computer that has 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 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\nAffected users should treat their systems as potentially under full external control and take comprehensive remediation steps accordingly."

Indicators of compromise

Packages
  • index-ulid

Remediation

  • Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the index-ulid package from all affected systems
  • Perform a comprehensive security audit of any system that had this package installed
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
  • Review access logs and audit trails for any suspicious activity during the period the package was installed

Sources

  1. GitHub Advisory GHSA-95pm-8vrw-2wrp · GitHub Advisory Database

Cite this entry

"Malware in index-ulid." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 15, 2026; last updated June 16, 2026. https://supplychainattack.org/incident/malware-in-index-ulid-1boj6c

Suggest a correction

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

Related incidents

  1. resolvedcritical

    Malicious code in test2221 (npm)

    The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.

    npmCompromised package
  2. containedcritical

    Malware in n8n-nodes-trust-me-im-totally-safe

    Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.

    npmCompromised package
  3. activecritical

    Malware in litespeed-cache

    Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.

    npmCompromised package
  4. containedcritical

    Malware in open-worker-cli

    Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.

    npmCompromised package