Which versions of moidevy are malicious?

The following npm versions of moidevy are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate moidevy if I installed it?

moidevy is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed moidevy — how do I know if it already compromised me?

If moidevy was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is moidevy part of a known attack campaign?

Yes — moidevy is associated with the IN-MAL-2026-018497 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find moidevy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for moidevy (version 1.0.0).

Malicious package

moidevynpm

Advisory published Aug 21, 2026Updated Aug 21, 2026

moidevy is a confirmed malicious npm package (MAL-2026-14348) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in moidevy (npm)

MAL-2026-14348

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall moidevy

What this malware does

main.js imports child_process 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 is not a documented public service and combined with child_process usage in the same module matches the shape of an installer-side data exfiltration / remote-command channel. The .internal TLD is non-routable on the public internet, suggesting either a lure destination or infrastructure meant to be resolved via a custom resolver on compromised hosts.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2eac79904b327f6508820c84c1350dd1bef3fc43eaf6e61d826f17ed5981d664

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for moidevy (version 1.0.0).
If you installed it — respond
moidevy is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If moidevy was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. moidevy on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018497

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks moidevy-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database