Malicious code in moidevy (npm)
The npm package moidevy contained malicious code that imports child_process and makes POST requests to a hardcoded endpoint at https://ipc.shadxino.internal, enabling remote command execution and data exfiltration on compromised systems.
- Disclosed
- Last updated
- Blast radius
- All npm users who installed the malicious moidevy package
- Ecosystems
- Attack vectors
- Affected entities
- moidevynpm package containing malicious code
The npm package moidevy was found to contain malicious code in its main.js file. The code imports the child_process module and issues POST requests to a hardcoded endpoint at https://ipc.shadxino.internal (referenced at lines 358 and 452, with POST calls at lines 364 and 368).
The destination domain is not a documented public service. The use of child_process combined with POST requests to an undocumented endpoint matches the pattern of installer-side data exfiltration and remote command execution. The .internal TLD is non-routable on the public internet, suggesting either a lure destination or infrastructure designed to be resolved via a custom resolver on compromised hosts.
The malicious package was identified by Amazon Inspector and credited to the OpenSSF's malicious-packages repository. This represents a direct compromise of the package supply chain, allowing attackers to execute arbitrary commands and exfiltrate data from systems that installed the affected version.
Indicators of compromise
- Packages
- moidevy
- Domains
- ipc.shadxino.internal
Remediation
- Immediately uninstall moidevy from all systems
- Audit npm package.lock and package.json files for moidevy dependencies
- Review system logs for suspicious POST requests to ipc.shadxino.internal or similar endpoints
- Check for signs of unauthorized command execution on systems that installed moidevy
- Update to a clean version of any package that depended on moidevy
- Consider full system audit and potential credential rotation on affected hosts
Sources
- GitHub Advisory GHSA-4j24-mrxm-5jfj · GitHub Advisory Database
Cite this entry
"Malicious code in moidevy (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 21, 2026; last updated August 21, 2026. https://supplychainattack.org/incident/malicious-code-in-moidevy-npm-1psbdj
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 svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - 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
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 - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package