Malware in leo-connector-elasticsearch
Malware was discovered in the npm package leo-connector-elasticsearch. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with leo-connector-elasticsearch installed or running
- Ecosystems
- Attack vectors
- Affected entities
- leo-connector-elasticsearch
The npm package leo-connector-elasticsearch was found to contain malware. GitHub Security Advisory GHSA-p5fw-hxvx-jq85 documents the incident.\n\nAny computer with this package installed or running should be considered fully compromised. The malware may grant outside entities full control of affected systems. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected computer.\n\nWhile the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise. Additional security measures and system hardening may be necessary.
Indicators of compromise
- Packages
- leo-connector-elasticsearch
Remediation
- Immediately remove leo-connector-elasticsearch from all systems
- Rotate all secrets, keys, and credentials stored on affected computers from a different, unaffected computer
- Perform a full security audit and malware scan of affected systems
- Consider rebuilding affected systems from clean media if full compromise is suspected
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Notify relevant stakeholders and security teams of the compromise
Sources
- GitHub Advisory GHSA-p5fw-hxvx-jq85 · GitHub Advisory Database
Cite this entry
"Malware in leo-connector-elasticsearch." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-leo-connector-elasticsearch-b8dw8f
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 github-policy-bot (npm)
The npm package github-policy-bot contained malicious code that exfiltrated host identifiers and environment metadata during installation via a postinstall script. The package name shadowed a legitimate Google-owned repository and was authored under a placeholder account claiming security research purposes.
npmCompromised packageTyposquatting - containedcritical
Malicious code in crypto-javas (npm)
The npm package crypto-javas contains malicious code in its postinstall hook and main entrypoint that harvests environment variables (including CI secrets like AWS_*, GITHUB_TOKEN, NPM_TOKEN) and exfiltrates them to an attacker-controlled backend. The package is presented deceptively as @wizlabs/js-crypto with a placeholder repository.
npmCompromised packageTyposquatting - containedcritical
Malicious code in flydev (npm)
The npm package flydev contains malicious code designed to destroy Windows systems. The package masquerades as a utility but executes destructive operations including filesystem deletion, process termination, memory exhaustion, and fork bombs when invoked.
npmCompromised package - containedcritical
Malicious code in npm-wold (npm)
npm-wold@1.1.1 contains malicious code in its postinstall script that fetches remote JSON from a hardcoded endpoint and dynamically invokes attacker-controlled functions with attacker-supplied arguments, enabling code execution at install time.
npmCompromised package