Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malware in temp-cloak

Malware was discovered in the npm package temp-cloak, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a different computer.

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

The npm package temp-cloak was found to contain malware. According to the GitHub Advisory (GHSA-rr2q-r4vq-r6cm), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated 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\nThe severity is critical due to the potential for complete system compromise and the risk of credential theft or lateral movement to other systems.

Indicators of compromise

Packages
  • temp-cloak

Remediation

  • Remove the temp-cloak package immediately from all systems
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Assume full system compromise and conduct forensic analysis if possible
  • Monitor affected systems for signs of unauthorized access or persistence mechanisms
  • Review system logs for any suspicious activity during the period the package was installed

Sources

  1. GitHub Advisory GHSA-rr2q-r4vq-r6cm · GitHub Advisory Database

Cite this entry

"Malware in temp-cloak." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 14, 2026. https://supplychainattack.org/incident/malware-in-temp-cloak-1oqqfa

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