Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in slds-lsp-client

Malware was discovered in the npm package slds-lsp-client, potentially providing full system compromise to attackers. 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
Attack vectors
Affected entities
  • slds-lsp-client

The npm package slds-lsp-client was found to contain malware. According to the GitHub advisory, any computer that has this package installed or running should be considered fully compromised, with all secrets and keys stored on that computer at risk.\n\nThe advisory recommends immediate rotation of all secrets and keys from a different, uncompromised computer. 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 initial compromise, given that the attacker may have gained full control of the affected system.\n\nThis incident was disclosed on 2026-07-14 via GitHub's advisory system.

Indicators of compromise

Packages
  • slds-lsp-client

Remediation

  • Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
  • Remove the slds-lsp-client package from all affected systems
  • Conduct a full security audit and forensic analysis of any system that had this package installed
  • Monitor affected systems for signs of persistent malware or unauthorized access
  • Review and revoke any credentials or API keys that may have been exposed

Sources

  1. GitHub Advisory GHSA-63pr-5274-mfh7 · GitHub Advisory Database

Cite this entry

"Malware in slds-lsp-client." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 14, 2026. https://supplychainattack.org/incident/malware-in-slds-lsp-client-75lhn8

Suggest a correction

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

  1. activecritical

    Malware in tme-xca-react

    Malware was discovered in the npm package tme-xca-react. 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
  2. activecritical

    Malware in @resolvx/core

    Malware was discovered in the npm package @resolvx/core. Systems with this package installed or running are considered fully compromised, requiring immediate rotation of all secrets and keys from a different computer.

    npmCompromised package
  3. activecritical

    Malware in @tonsdk/core

    Malware was discovered in the npm package @tonsdk/core. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  4. activecritical

    Malware in @aonunited/angular

    Malware discovered in the npm package @aonunited/angular. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package