If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (de40a55476bbcc5eda275f9f385396699f1b066bf1ddedb80fad053c4057c63a)
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.
Source: ghsa-malware (9cae12d795a901843e179a21778555597220721130f13c98674c03c9adecf984)
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.