@hrmony/kit-5 (npm) · Malicious Code
Affects @hrmony/kit-5Source GCVE Database
Malicious package : remove @hrmony/kit-5 and rotate any secrets on hosts that installed it.
Data as of 29 Sep 2026, 21:04 UTC
Malicious package
Published to npm · OSV MAL-2026-17266
What to do
Remove @hrmony/kit-5 from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@hrmony/kit-5 | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (6457aa73ec15f68e06005977033aaba349467d40e3d406f0810684a43b74fcb5) The package's preinstall script and its main entry (index.js) both perform identical credential-harvesting: they query the EC2 Instance Metadata Service (IMDSv2) at 169.254.169.254 for the identity document and IAM role security credentials, enumerate the entire process.env, and recursively read /var/run/secrets/ (Kubernetes service-account tokens and mounted secrets). The collected data is POSTed to a hardcoded attacker-controlled host at hrnmn.dd.h4x.tv (paths /save_instance_info_hook from preinstall and /save_instance_info_index from index.js). The destination is unrelated to any legitimate package purpose, there is no user configuration, and the behavior fires automatically on `npm install` via the preinstall lifecycle hook as well as on any `require()`/`import` of the package. The harvested material — temporary AWS IAM credentials, cloud instance identity, arbitrary environment variables (which routinely contain API keys, tokens, and database credentials in CI/build environments), and Kubernetes service-account tokens — grants immediate cross-service access to the installer's cloud and cluster resources. ## Source: ghsa-malware (07386b2d1e2efa71fd38c591953684c11302ad77f1c7943bd542b71fd83184e3) 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.