Malware in @one-chat/react
Malware was discovered in the npm package @one-chat/react. Systems with this package installed or running are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @one-chat/react
The npm package @one-chat/react was found to contain malware. According to the GitHub Security Advisory (GHSA-598h-mgjc-c42f), 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 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 installation, given the potential for full system compromise.\n\nUsers should treat any system that has run this package as potentially containing persistent malware and take appropriate containment and recovery measures.
Indicators of compromise
- Packages
- @one-chat/react
Remediation
- Immediately isolate any computer that has installed or run @one-chat/react from the network
- Rotate all secrets, API keys, credentials, and sensitive data from a different, uncompromised computer
- Remove the @one-chat/react package from all systems
- Perform a full security audit and malware scan of affected systems
- Consider the affected system as potentially compromised and plan for full rebuild or forensic analysis
- Review access logs and audit trails for any unauthorized activity on affected systems
Sources
- GitHub Advisory GHSA-598h-mgjc-c42f · GitHub Advisory Database
Cite this entry
"Malware in @one-chat/react." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 31, 2026; last updated August 1, 2026. https://supplychainattack.org/incident/malware-in-one-chat-react-762ezx
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