@hrmony/pladddform-frontendnpm
@hrmony/pladddform-frontend is a confirmed malicious npm package (MAL-2026-17276) that steals credentials and exfiltrates sensitive data (malicious versions 48.99.0, 49.3.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @hrmony/pladddform-frontend (npm)
What this malware does
@hrmony/[email protected] ships an index.js whose top-level code, executed on require/import, POSTs to the hardcoded attacker host https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-frontend and then invokes two harvesters. aws_get() queries the AWS EC2 Instance Metadata Service at 169.254.169.254 using IMDSv2 (PUT /latest/api/token) and sweeps /latest/meta-data/iam/security-credentials/ to collect instance identity, IAM role names, and temporary IAM security credentials. local_get() enumerates every entry of process.env and recursively reads /var/run/secrets/, capturing Kubernetes-mounted service-account tokens and secret files. Both payloads are POSTed to the same hardcoded hrnmn.dd.h4x.tv endpoint. The package has an empty description, no functional code beyond the stealer, an intentionally misspelled scope and name mimicking an internal 'harmony/platform-frontend', and declares a dependency on the similarly look-alike '@hrmony/kit-5', consistent with a dependency-confusion typosquat targeting an internal package name.
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/pladddform-frontend (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/pladddform-frontend across your stack and pipelines.
If you installed it — respond
@hrmony/pladddform-frontend 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/pladddform-frontend 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/pladddform-frontend 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/pladddform-frontend-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.