Malicious code in @hrmony/benefitverwaltung (npm)

CISA 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.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (a567d870fdf9c4fecac3e9fbb009a5b23e4450ea608d416564095680dc5bc4b2) On top-level import, the package's main module POSTs an initial identifying beacon (body {"c53":"hello"}) to the hardcoded endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_benefitverwaltung, then performs three concrete harvest steps and exfiltrates each to the same host: (1) an IMDSv2 request flow against 169.254.169.254 that reads instance identity, enumerates IAM role names under /iam/security-credentials/, and fetches the temporary AWS access key ID, secret access key, and session token for each role; (2) a full enumeration of process.env via Object.entries(process.env) into an envs object; (3) a recursive read of /var/run/secrets/ collecting Kubernetes-mounted service-account tokens and secret files. The collected data is sent via fetch(EXPORTER_URL, {method: 'POST', body: JSON.stringify(...)}). The destination domain h4x.tv is not associated with the @hrmony scope or any legitimate benefit-administration service. The package also declares a runtime dependency on @hrmony/kit-5 ^1.0.0 within its own scope while shipping only exfiltration code as its main, consistent with a dependency-confusion lure targeting an internal @hrmony namespace. ## Source: ghsa-malware (f80eb89dea9e90cc0c617b5ee104b8c0acdccd2ac8110906c11d0d90685ecc52) 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:45 UTC

Source modified

29 Sep 2026 17:30:15 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.