@hrmony/benefit-sachbezugnpm
Advisory published Updated
@hrmony/benefit-sachbezug is a confirmed malicious npm package (MAL-2026-17256) 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/benefit-sachbezug (npm)
What this malware does
The package's main entry (index.js) executes at require/import time and POSTs harvested data to the hardcoded endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_benefit-sachbezug. One path queries the AWS EC2 Instance Metadata Service (IMDSv2), obtains a token via PUT to /latest/api/token, and retrieves the instance identity document, IAM role temporary credentials via iam/security-credentials/, network and security-group metadata, and user-data. A second path enumerates all process.env entries and recursively reads /var/run/secrets/, the standard mount path for Kubernetes service-account tokens and mounted secrets, and sends both to the same author-controlled host. The package name (@hrmony/benefit-sachbezug), empty description, ISC license, and beacon body {"c53":"hello"} with the endpoint path keyed to the scope name match the dependency-confusion beacon pattern targeting an internal @hrmony scope.
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
Search your lockfiles and build artifacts for @hrmony/benefit-sachbezug (version 1.99.0).
If you installed it — respond
@hrmony/benefit-sachbezug 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/benefit-sachbezug was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @hrmony/benefit-sachbezug-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.