Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in remarkable-table

Malware discovered in the npm package remarkable-table. The package is considered to provide full system compromise to any computer where it is installed or running.

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

A critical malware incident has been identified in the npm package remarkable-table. According to the GitHub Advisory (GHSA-pw78-w6gv-hfcr), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the malicious package may have granted outside entities full control of affected systems. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected computer.\n\nWhile removing the package is recommended, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package installation, given the level of system access the malware appears to have obtained.

Indicators of compromise

Packages
  • remarkable-table

Remediation

  • Immediately remove the remarkable-table package from all systems
  • Rotate all secrets, keys, and credentials from a different, unaffected computer
  • Assume full system compromise and conduct forensic analysis
  • Monitor affected systems for signs of persistent malware or backdoors
  • Review system logs and network traffic for indicators of compromise
  • Consider rebuilding affected systems from clean media if possible

Sources

  1. GitHub Advisory GHSA-pw78-w6gv-hfcr · GitHub Advisory Database

Cite this entry

"Malware in remarkable-table." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 13, 2026; last updated July 13, 2026. https://supplychainattack.org/incident/malware-in-remarkable-table-rl24ku

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