Malware in ldapaotest
The npm package ldapaotest was found to contain malware, resulting in full system compromise for any computer with the package installed or running. All secrets and keys should be rotated immediately from a different computer, and the package should be removed.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- ldapaotestnpm package containing malware
The npm package ldapaotest was identified as containing malware. According to the GitHub Advisory (GHSA-67gf-qg4g-4qfw), any computer that has 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 computer. 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 initial compromise, given that the outside entity may have gained full control of the system.\n\nUsers should treat any system that installed or ran this package as potentially fully compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- ldapaotest
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the ldapaotest package from all affected systems
- Conduct a full security audit and forensic analysis of any system that installed or ran the package
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider rebuilding affected systems from clean media if full compromise is suspected
Sources
- GitHub Advisory GHSA-67gf-qg4g-4qfw · GitHub Advisory Database
Cite this entry
"Malware in ldapaotest." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 24, 2026; last updated June 24, 2026. https://supplychainattack.org/incident/malware-in-ldapaotest-13bz1r
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in pretie_x2
The npm package pretie_x2 contains malware that grants full control of affected systems. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in html-to-gutenberg
The npm package html-to-gutenberg was found to contain malware. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in eth_accounts
Malware was discovered in the eth_accounts npm package. Any computer with this package installed is considered fully compromised and all secrets and keys should be rotated immediately from a different machine.
npmCompromised package - activecritical
Malware in multer-express
Malware was discovered in the npm package multer-express. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package