Malicious code in @hd-team/app-dnpkg-beta (npm)
MAL-2026-14569 · GHSA-6p53-v557-745c
Published · Modified
Dependency scanning
Check whether @hd-team/app-dnpkg-beta is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (8f5be2650e129e66738602f02b893ba443ffbd9a47df685f76bd4ae84b885529)
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.
Source: ghsa-malware (582441b42ca54807958c70a35052a769d2a762fc80ef7db1de55df2f40821926)
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.
Ready to move
Start Securing
Free, no credit card | First findings in minutes