Malware in uidai_reusable_components
Malware was discovered in the npm package uidai_reusable_components. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- uidai_reusable_components
A critical malware incident was identified in the npm package uidai_reusable_components. According to the GitHub advisory, any system that has installed or executed this package should be treated as fully compromised.\n\nThe advisory warns that all secrets, keys, and credentials stored on affected computers must be rotated immediately from a different, uncompromised system. While the malicious package can 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, as the attacker may have gained full control of the system.\n\nThe incident was disclosed on 2026-06-18 via GitHub's advisory system.
Indicators of compromise
- Packages
- uidai_reusable_components
Remediation
- Immediately remove the uidai_reusable_components package from all systems
- Rotate all secrets, keys, and credentials from a different, uncompromised computer
- Conduct a full security audit of any system that had this package installed
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Review package dependencies to identify any other potentially compromised packages
Sources
- GitHub Advisory GHSA-8gm2-m96j-547g · GitHub Advisory Database
Cite this entry
"Malware in uidai_reusable_components." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 18, 2026; last updated June 20, 2026. https://supplychainattack.org/incident/malware-in-uidai-reusable-components-uaagp6
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