Malicious code in @hrmony/component-library (npm)
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
osv · MAL-2026-17259
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (a93efe09ed89a9899669e54f614f80d91a80c59d77e0c2a2f673f92590488804) index.js (declared as the package main) runs top-level async code on require/import that performs three exfiltration actions against a hardcoded attacker endpoint https://hrnmn.dd.h4x.tv/. First, it POSTs a fixed beacon identifying the package to /save_instance_info_from_pkge_hrmony_component-library. Second, it queries the AWS EC2 Instance Metadata Service at 169.254.169.254 using IMDSv2, enumerates IAM roles, and reads iam/security-credentials/{role} to collect temporary AWS access keys along with the identity document and user-data, then POSTs the collected object to the same host. Third, it iterates every entry of process.env and recursively reads all files under /var/run/secrets/ (Kubernetes service-account tokens and mounted secrets) and POSTs them to the same host. The package ships no component-library code; the exfiltration payload is its only behavior. The scope name @hrmony (missing the 'a' from @harmony) and the abnormally high 28.99.0 version are consistent with typosquat and dependency-confusion targeting. ## Source: ghsa-malware (43173bc756c5c7bb307d748364b7436b5691bd972fa14c3ab6f51a4a510aeafd) 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:32:05 UTC
- Source modified
- 29 Sep 2026 17:30:14 UTC
- Observed 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
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.