Malicious code in @hrmony/lohndateien (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 (743e2b2a4a3cf2758e6eb457dbc47857751d31379b13a48a2da25fc23f8e9701) index.js executes on module load and performs three attacker-beneficial actions against a hardcoded remote endpoint at https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_lohndateien. First, an unconditional POST beacon ({"c53":"hello"}) signals a successful install/import. Second, the module queries the AWS instance metadata service at 169.254.169.254 using IMDSv2 (PUT /latest/api/token) to enumerate instance identity, user-data, and IAM role security credentials from /latest/meta-data/iam/security-credentials/, then POSTs the collected object to the same host. Third, local_get() iterates process.env into a dictionary and recursively reads /var/run/secrets/ (Kubernetes service-account tokens and mounted secret files), POSTing both structures to the same endpoint. The destination host is unrelated to any declared publisher infrastructure and the URL path embeds the package name, consistent with a targeted dependency-confusion or supply-chain attack. Installing and loading this package on an EC2 host or in a Kubernetes workload yields the attacker full AWS role credentials, all environment variables (including secrets and tokens), and any mounted Kubernetes secrets. ## Source: ghsa-malware (b4d72aaf224d02f991bc113168187540eae0db2345f5bad0f24f82ea76433906) 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:29:39 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.