Malware in tick-forge
Malware discovered in the npm package tick-forge. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with tick-forge installed or running
- Ecosystems
- Attack vectors
- Affected entities
- tick-forge
A critical malware incident has been identified in the npm package tick-forge. According to the GitHub Advisory (GHSA-rjvw-v893-2f7g), any system that has installed or executed this package should be treated as fully compromised.\n\nThe advisory recommends immediate action: all secrets and cryptographic keys stored on affected computers must be rotated 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 deployed during the compromise, as the attacker may have gained full control of the affected system.\n\nAffected users should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- tick-forge
Remediation
- Immediately rotate all secrets, API keys, and cryptographic credentials from a different, uncompromised computer
- Remove the tick-forge package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had tick-forge installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider full system reimaging if complete compromise is suspected
Sources
- GitHub Advisory GHSA-rjvw-v893-2f7g · GitHub Advisory Database
Cite this entry
"Malware in tick-forge." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-tick-forge-1otfui
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package