Malicious code in @hrmony/interfaces (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-17262
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b7837cf2dff543cfea2f35e0dea5f767ca7b8e8f81129f4c770e5693ed247c0e) index.js executes top-level async code on any require/import of the package. The code (1) obtains an AWS IMDSv2 token and fetches EC2 instance identity, IAM role temporary security credentials from /latest/meta-data/iam/security-credentials/<role> and identity-credentials/ec2/security-credentials/ec2-instance, plus user-data and network metadata; (2) serializes the full process.env; (3) recursively reads /var/run/secrets/, which on Kubernetes contains service-account tokens and mounted secrets; and (4) POSTs the aggregated JSON to the hardcoded endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_interfaces. The package ships a single ~5KB file with an empty description under the name @hrmony/interfaces (resembling a private/internal scope), and the exfiltration URL path is tagged per-package, consistent with a dependency-confusion campaign. The exfiltrated IAM role credentials grant AWS API access under the installing host's role; captured environment variables and Kubernetes service-account tokens grant further access to CI, build, and cluster resources. ## Source: ghsa-malware (5d6d5cfe23b3b7df212ed46cf25538924fdd51f783172b822c93e38e7d7a16ed) 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:33:47 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.