Malware in markable-table
Malware discovered in the npm package markable-table. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with markable-table installed or running
- Ecosystems
- Attack vectors
- Affected entities
- markable-table
A critical malware incident has been identified in the npm package markable-table. According to the GitHub Advisory (GHSA-qc34-pqm6-35rf), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the compromise is severe enough that all secrets and keys stored on affected computers should be rotated immediately from a different, unaffected 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 that resulted from the installation.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for widespread impact across all systems that have installed or executed this package.
Indicators of compromise
- Packages
- markable-table
Remediation
- Immediately isolate any system with markable-table installed from the network
- Rotate all secrets, API keys, and credentials from a clean, unaffected computer
- Remove the markable-table package from all affected systems
- Conduct a full forensic analysis of affected systems to identify any additional malicious software
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if compromise is confirmed
- Audit any systems that may have been accessed using credentials stored on compromised machines
Sources
- GitHub Advisory GHSA-qc34-pqm6-35rf · GitHub Advisory Database
Cite this entry
"Malware in markable-table." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 13, 2026; last updated July 13, 2026. https://supplychainattack.org/incident/malware-in-markable-table-1r7jim
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system 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 - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit