Malicious code in @hd-team/app-dnpkg-beta (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-14569
Published--- _-= Per source details. Do not edit below this line.=-_ ## 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.
- Source published
- 27 Aug 2026 21:49:39 UTC
- Source modified
- 28 Aug 2026 15:15:11 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.