Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in sso-users-detection

The npm package sso-users-detection was found to contain malware, resulting in full system compromise of any computer with the package installed or running. GitHub Security Advisory GHSA-x9p4-637q-6wjw documents the incident.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • sso-users-detection

The npm package sso-users-detection was identified as containing malware. According to the GitHub Security Advisory, 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, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software resulting from the installation.\n\nThis represents a critical supply chain compromise affecting the npm ecosystem.

Indicators of compromise

Packages
  • sso-users-detection

Remediation

  • Immediately rotate all secrets and keys from a different, uncompromised computer
  • Remove the sso-users-detection package from all affected systems
  • Assume full system compromise and conduct forensic analysis
  • Audit all systems that had this package installed for signs of unauthorized access or data exfiltration
  • Review and revoke any credentials or API keys that may have been exposed

Sources

  1. GitHub Advisory GHSA-x9p4-637q-6wjw · GitHub Advisory Database

Cite this entry

"Malware in sso-users-detection." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 31, 2026; last updated August 1, 2026. https://supplychainattack.org/incident/malware-in-sso-users-detection-hz7i4j

Suggest a correction

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

  1. resolvedcritical

    Malware in test-dev-exec

    The npm package test-dev-exec contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package
  2. resolvedcritical

    Malware in test-dev-link

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

    npmCompromised package
  3. resolvedcritical

    Malware in @moxfive-llc/common

    Malware was discovered in the npm package @moxfive-llc/common. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.

    npmCompromised package
  4. resolvedcritical

    Malware in test-dev-dispatch

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

    npmCompromised package