Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in sams-sr-sdk-h5

Malware discovered in the npm package sams-sr-sdk-h5. 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
  • sams-sr-sdk-h5

The npm package sams-sr-sdk-h5 has been identified as containing malware. According to the GitHub advisory (GHSA-3r2r-29px-gqp6), 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 package's execution, given the potential for full system compromise.\n\nAffected users should treat this as a critical security incident requiring immediate action.

Indicators of compromise

Packages
  • sams-sr-sdk-h5

Remediation

  • Immediately remove the sams-sr-sdk-h5 package from all affected systems
  • Rotate all secrets, API keys, and credentials stored on compromised systems from a different, uncompromised computer
  • Perform a full security audit and malware scan of affected systems
  • Monitor affected systems for signs of unauthorized access or persistence mechanisms
  • Consider rebuilding affected systems from clean media if full compromise is suspected

Sources

  1. GitHub Advisory GHSA-3r2r-29px-gqp6 · GitHub Advisory Database

Cite this entry

"Malware in sams-sr-sdk-h5." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 14, 2026. https://supplychainattack.org/incident/malware-in-sams-sr-sdk-h5-184rei

Suggest a correction

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

  1. containedcritical

    Malware in @logdna-web/styles

    Malware was discovered in the npm package @logdna-web/styles. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  2. activecritical

    Malware in @flex-ng/filter-pipe

    Malware discovered in the npm package @flex-ng/filter-pipe. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  3. activecritical

    Malware in @idms-corp/auth-ui

    Malware discovered in the npm package @idms-corp/auth-ui. Systems with this package installed are considered fully compromised, with potential for complete system takeover.

    npmCompromised package
  4. activecritical

    Malware in salesforce-vscode-slds

    Malware was discovered in the npm package salesforce-vscode-slds. Any system with this package installed is considered fully compromised and poses a critical risk to stored secrets and keys.

    npmCompromised package