@hrmony/pladddform-codegen
Affected
- Versions:
49.99.0
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-4jh6-g3hw-7qjc
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in @hrmony/pladddform-codegen (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (58f0706d7223f8a1ff87ac80c6e1e42af148214545e55acc865cce12fee7eec4)
On module load, index.js unconditionally beacons to the hardcoded non-first-party endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-codegen and then performs three credential-harvest flows against the installer: (1) queries the AWS instance metadata service at 169.254.169.254 (IMDSv2), enumerates IAM role names, retrieves each role's security credentials, and collects the EC2 identity document, user-data, and network-interface metadata; (2) enumerates all process.env entries; (3) recursively reads /var/run/secrets/ (Kubernetes projected service-account tokens and mounted secrets). The collected data is POSTed to the same hardcoded attacker host. The package name is a typosquat of an @hrmony scoped package with an inflated version (49.99.0) consistent with a dependency-confusion attempt, and it declares an internal-looking sibling dependency @hrmony/kit-5. The exfiltration URL path embeds the package name, indicating a campaign-style beacon per lure.
Source: ghsa-malware (7506445769ecafceaa9997f0a2e50c59f9573d93d70ac74c88e105477033f05a)
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.
Not rated by the source.
49.99.0None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0