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

dandh8112npm

dandh8112 is a confirmed malicious npm package (MAL-2025-49730) that executes malicious code on install (malicious versions 1.9.5, 1.9.6, 1.9.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dandh8112 (npm)

MAL-2025-49730
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dandh8112

What this malware does

The package dandh8112 was found to contain 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.

The OpenSSF Package Analysis project identified 'dandh8112' @ 1.9.7 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged
1.9.51.9.61.9.7

Indicators of compromise (SHA-256)

439693dc034f10b79277c48f7d3457adc09a623d5d067afa83543f5393f8825e
06f2bb5fabeb29dfa7cd1921c6c28f491ec017dddaae26b427f956b1f5f3c288
1feb876cf4ecc10359bb099b8248f264c6f4f4955b287d80311bdebdc49abadb
d6d669c4a9f484f82a17b41c7a26f94b497d9b554636d6ec620fc74a04f69b93
ec209aad5fe546d172d6b28d0ec35285e624992da292d0736ba5057302461095

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 dandh8112 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dandh8112 across your stack and pipelines.

  2. If you installed it — respond

    Remove dandh8112 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 dandh8112 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 dandh8112 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. dandh8112 on npm has been identified as a malicious package (versions 1.9.5, 1.9.6, 1.9.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xjwg-crqx-2288

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks dandh8112-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

dandh8112 (npm) malicious package — MAL-2025-49730 | O3 Security