Malware in dsilva-react-module-seed
Malware discovered in the npm package dsilva-react-module-seed. Systems with this package installed 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
- dsilva-react-module-seed
A malicious package named dsilva-react-module-seed was published to npm and contains malware. Any computer that has installed or run this package should be considered fully compromised.\n\nThe malware grants outside entities full control of affected systems. All secrets, keys, and credentials stored on compromised machines must be rotated immediately from a different, unaffected computer.\n\nWhile 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 initial compromise. Complete system remediation may be necessary.
Indicators of compromise
- Packages
- dsilva-react-module-seed
Remediation
- Immediately remove the dsilva-react-module-seed package from all systems
- Rotate all secrets, keys, and credentials from a different, unaffected computer
- Assume full system compromise and perform comprehensive security audit
- Consider complete system rebuild or forensic analysis to identify all malicious artifacts
- Check for lateral movement and compromise of other systems on the network
- Monitor affected systems for signs of ongoing malicious activity
Sources
- GitHub Advisory GHSA-qrv2-rr4v-8g54 · GitHub Advisory Database
Cite this entry
"Malware in dsilva-react-module-seed." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 30, 2026; last updated July 30, 2026. https://supplychainattack.org/incident/malware-in-dsilva-react-module-seed-1tx0po
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