Malware in leo-connector-mongo
Malware was discovered in the npm package leo-connector-mongo. Systems with this package installed or running are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with leo-connector-mongo installed or running
- Ecosystems
- Attack vectors
- Affected entities
- leo-connector-mongo
The npm package leo-connector-mongo was found to contain malware. According to the GitHub Advisory (GHSA-gwx3-mrcv-2c26), any computer with 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 system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a critical supply chain compromise affecting all users of the leo-connector-mongo package.
Indicators of compromise
- Packages
- leo-connector-mongo
Remediation
- Immediately isolate any system with leo-connector-mongo installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the leo-connector-mongo package from all affected systems
- Conduct a full forensic analysis of affected systems to identify any additional malicious software
- Review system logs and access patterns for signs of unauthorized activity
- Consider full system reimaging if compromise is confirmed
Sources
- GitHub Advisory GHSA-gwx3-mrcv-2c26 · GitHub Advisory Database
Cite this entry
"Malware in leo-connector-mongo." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-leo-connector-mongo-fq1jxr
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 rust-testing-utils (npm)
The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.
npmCompromised packageMalicious commit - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malware in hydration-dim-kit
Malware was discovered in the npm package hydration-dim-kit. Any computer 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