Which versions of ndmckauxuoincv are malicious?

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

How do I remediate ndmckauxuoincv if I installed it?

Remove ndmckauxuoincv from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If ndmckauxuoincv was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ndmckauxuoincv part of a known attack campaign?

Yes — ndmckauxuoincv is associated with the GHSA-q5vm-6mhj-qq8c, IN-MAL-2026-020377 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 ndmckauxuoincv across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ndmckauxuoincv (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ndmckauxuoincv across your stack and pipelines.

Malicious package

ndmckauxuoincvnpm

ndmckauxuoincv is a confirmed malicious npm package (MAL-2026-16401) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ndmckauxuoincv (npm)

MAL-2026-16401

Immediate action

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

npm uninstall ndmckauxuoincv

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b2ead64a8b8d2576b6de636600ea433cdb579cbbf3a0aea98bb0d3c23f041d03

dfd29f430051fb1e4809ff59728851a683aa0fc25eabec2f807067e928245222

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ndmckauxuoincv (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ndmckauxuoincv across your stack and pipelines.
If you installed it — respond
Remove ndmckauxuoincv from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ndmckauxuoincv was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ndmckauxuoincv before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ndmckauxuoincv 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

GHSA-q5vm-6mhj-qq8cIN-MAL-2026-020377

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ndmckauxuoincv-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database