Malicious code in @hrmony/pladddform-shared-infrastructure (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 (89319d39ad6d753459be90c221d657a73f70955c63d1675b347c11b5743209cc) On module import, index.js executes three exfiltration routines that POST harvested secrets to the hardcoded endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-shared-infrastructure. (1) A beacon POST with body {"c53":"hello"} fires first to confirm the victim. (2) aws_get() queries the AWS Instance Metadata Service at 169.254.169.254 (IMDSv2) for instance identity, EC2 security credentials, and iterates /iam/security-credentials/ to retrieve every attached IAM role's temporary credentials, then ships the aggregated JSON to the attacker host. (3) local_get() enumerates all process.env variables and recursively reads /var/run/secrets/ (Kubernetes service-account tokens and mounted secret volumes), POSTing both to the same host. The package name resembles an internal-looking scope (@hrmony/pladddform-shared-infrastructure with a typo in 'pladddform') consistent with a dependency-confusion lure, and declares a dependency on @hrmony/kit-5 in the same author-controlled scope that would be pulled in on install. Any host importing this package on EC2 or in Kubernetes loses its cloud IAM credentials, workload identity, and full process environment to the attacker. ## Source: ghsa-malware (491f8f3411beacd1ac0faacca34f123868acfc2fb54242408efe6b186265a1fe) 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:18 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.