Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @hd-team published 8 malicious packages. See the full campaign →
Malicious package

@hd-team/app-dnpkg-betanpm

Advisory published Updated

@hd-team/app-dnpkg-beta is a confirmed malicious npm package (MAL-2026-14569) that steals credentials and exfiltrates sensitive data (malicious version 1.0.20260808153500). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @hd-team/app-dnpkg-beta (npm)

MAL-2026-14569
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @hd-team/app-dnpkg-beta

What this malware does

The tarball contains only package.json and index.js. index.js is not JavaScript source: it is a base64-encoded JSON blob that decodes to a configuration object containing a cdn field whose value base64-decodes to the string 'funnull' (a CDN provider previously sanctioned for hosting malicious content), a domain field of https://apiyf.dq87771.com, an additional endpoint https://api.dq87771.com, and a hardcoded token (800cf3d509b44bf7bfd32529dc3ff597). The package declares no lifecycle scripts and index.js is not valid JavaScript, so npm install and require() of this package alone do not execute code. The shape — a non-functional package that carries only remote-configuration data pointing at Funnull-tagged infrastructure and an authentication token — is consistent with the config half of a two-package loader/config split, where a companion package reads this configuration to fetch and execute payloads from the referenced hosts.

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.20260808153500

Indicators of compromise (SHA-256)

582441b42ca54807958c70a35052a769d2a762fc80ef7db1de55df2f40821926
8f5be2650e129e66738602f02b893ba443ffbd9a47df685f76bd4ae84b885529

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @hd-team/app-dnpkg-beta (version 1.0.20260808153500).

  2. If you installed it — respond

    @hd-team/app-dnpkg-beta 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.

  3. Did it already run?

    If @hd-team/app-dnpkg-beta 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. @hd-team/app-dnpkg-beta on npm has been identified as a malicious package (version 1.0.20260808153500 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6p53-v557-745cIN-MAL-2026-018799

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @hd-team/app-dnpkg-beta-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@hd-team/app-dnpkg-beta (npm) malicious package — MAL-2026-14569 | O3 Security