Malicious code in @hrmony/pladddform-codegen (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-17273
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (58f0706d7223f8a1ff87ac80c6e1e42af148214545e55acc865cce12fee7eec4) On module load, index.js unconditionally beacons to the hardcoded non-first-party endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-codegen and then performs three credential-harvest flows against the installer: (1) queries the AWS instance metadata service at 169.254.169.254 (IMDSv2), enumerates IAM role names, retrieves each role's security credentials, and collects the EC2 identity document, user-data, and network-interface metadata; (2) enumerates all process.env entries; (3) recursively reads /var/run/secrets/ (Kubernetes projected service-account tokens and mounted secrets). The collected data is POSTed to the same hardcoded attacker host. The package name is a typosquat of an @hrmony scoped package with an inflated version (49.99.0) consistent with a dependency-confusion attempt, and it declares an internal-looking sibling dependency @hrmony/kit-5. The exfiltration URL path embeds the package name, indicating a campaign-style beacon per lure. ## Source: ghsa-malware (7506445769ecafceaa9997f0a2e50c59f9573d93d70ac74c88e105477033f05a) 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
- 29 Sep 2026 16:31:55 UTC
- Source modified
- 29 Sep 2026 17:30:14 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.