Malware in @ci-lifecycle-test/postinstall-ping
Malware was distributed via the npm package @ci-lifecycle-test/postinstall-ping. 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
- @ci-lifecycle-test/postinstall-ping
The npm package @ci-lifecycle-test/postinstall-ping contained malware that compromised any system where it was installed or executed. According to the GitHub Security Advisory (GHSA-q86v-7cxj-6979), any computer running this package should be considered fully compromised.\n\nThe malware granted outside entities full control of affected systems. Users are advised to rotate all secrets and keys from a different, uncompromised computer. While the 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.\n\nThis incident was disclosed on 2026-07-27 via GitHub's advisory system.
Indicators of compromise
- Packages
- @ci-lifecycle-test/postinstall-ping
Remediation
- Immediately remove the @ci-lifecycle-test/postinstall-ping package from all systems
- Rotate all secrets, keys, and credentials from a different, uncompromised computer
- Perform a full security audit and malware scan of any system that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved
Sources
- GitHub Advisory GHSA-q86v-7cxj-6979 · GitHub Advisory Database
Cite this entry
"Malware in @ci-lifecycle-test/postinstall-ping." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 27, 2026. https://supplychainattack.org/incident/malware-in-ci-lifecycle-test-postinstall-ping-gcluwl
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