Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

ndmcjcxiebysfdbnpm

ndmcjcxiebysfdb is a confirmed malicious npm package (MAL-2026-16400) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ndmcjcxiebysfdb (npm)

MAL-2026-16400
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ndmcjcxiebysfdb

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

3 flagged
1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

cb5a86c3600fb60247dd1969b1d80db9f9a17c74b0dc50519bcb3e37bbae6fff
5d6d78591ddbd2abc8045f5bdbe7694d000b3508dc8df6393ffd46d093351ef4
80d7417f66282fbf4fe0d426163c024e50687c20dbcbe06bed0034285d6e75b8
ac450c78e5165c1bd1251feac89c9de7795d15099b5d9858f3b747342072f888

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove ndmcjcxiebysfdb 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.

  3. Did it already run?

    If ndmcjcxiebysfdb 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.

  4. How O3 protects you

    O3 blocks ndmcjcxiebysfdb 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. ndmcjcxiebysfdb on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8344-w2r2-rxp2IN-MAL-2026-020375IN-MAL-2026-020376IN-MAL-2026-020378

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ndmcjcxiebysfdb-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.

Explore

ndmcjcxiebysfdb (npm) malicious package — MAL-2026-16400 | O3 Security