@hrmony/app-gateway-templatesnpm
@hrmony/app-gateway-templates is a confirmed malicious npm package (MAL-2026-17251) that steals credentials and exfiltrates sensitive data (malicious version 0.0.51). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @hrmony/app-gateway-templates (npm)
What this malware does
On require/import of @hrmony/app-gateway-templates, index.js (the package main) executes an exfiltration routine against a hardcoded attacker endpoint at https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_app-gateway-templates. The routine performs an AWS IMDSv2 token PUT against 169.254.169.254, then uses that token to read instance identity, IAM role security-credentials (temporary AWS access key, secret key, and session token), and network metadata. It also enumerates process.env in full and recursively reads /var/run/secrets/, which on Kubernetes pods contains mounted service-account tokens and application secrets. All collected data is POSTed to the same attacker endpoint. The package name is a one-character drop from harmony and declares a runtime dependency on @hrmony/kit-5 in the same typosquat scope, so installing this package also pulls additional attacker-controlled code under the same scope.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @hrmony/app-gateway-templates (version 0.0.51). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/app-gateway-templates across your stack and pipelines.
If you installed it — respond
@hrmony/app-gateway-templates is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @hrmony/app-gateway-templates was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @hrmony/app-gateway-templates before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @hrmony/app-gateway-templates-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.