@hrmony/api-gateway-service-confignpm
@hrmony/api-gateway-service-config is a confirmed malicious npm package (MAL-2026-17250) that steals credentials and exfiltrates sensitive data (malicious version 0.99.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @hrmony/api-gateway-service-config (npm)
What this malware does
index.js runs a top-level await fetch(...) on import that harvests installer host secrets and posts them to the hardcoded attacker endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_api-gateway-service-config. The code obtains an IMDSv2 token from 169.254.169.254, reads iam/security-credentials/<role> to collect short-lived AWS STS access keys, pulls instance identity, user-data, and network info, enumerates all of process.env, and recursively reads /var/run/secrets/ to capture Kubernetes service-account tokens and mounted secrets, then POSTs the aggregated JSON to the attacker host. The package also declares a single dependency on an unpublished scoped name @hrmony/kit-5 (^1.0.0), a shape consistent with a dependency-confusion campaign against an internal @hrmony/* namespace. Merely installing and importing this package causes theft of cloud IAM credentials and cluster secrets from the host.
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/api-gateway-service-config (version 0.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/api-gateway-service-config across your stack and pipelines.
If you installed it — respond
@hrmony/api-gateway-service-config 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/api-gateway-service-config 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/api-gateway-service-config 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/api-gateway-service-config-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.