@hrmony/pladddform-shared-infrastructurenpm
@hrmony/pladddform-shared-infrastructure is a confirmed malicious npm package (MAL-2026-17279) that steals credentials and exfiltrates sensitive data (malicious version 40.14.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @hrmony/pladddform-shared-infrastructure (npm)
What this malware does
On module import, index.js executes three exfiltration routines that POST harvested secrets to the hardcoded endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-shared-infrastructure. (1) A beacon POST with body {"c53":"hello"} fires first to confirm the victim. (2) aws_get() queries the AWS Instance Metadata Service at 169.254.169.254 (IMDSv2) for instance identity, EC2 security credentials, and iterates /iam/security-credentials/ to retrieve every attached IAM role's temporary credentials, then ships the aggregated JSON to the attacker host. (3) local_get() enumerates all process.env variables and recursively reads /var/run/secrets/ (Kubernetes service-account tokens and mounted secret volumes), POSTing both to the same host. The package name resembles an internal-looking scope (@hrmony/pladddform-shared-infrastructure with a typo in 'pladddform') consistent with a dependency-confusion lure, and declares a dependency on @hrmony/kit-5 in the same author-controlled scope that would be pulled in on install. Any host importing this package on EC2 or in Kubernetes loses its cloud IAM credentials, workload identity, and full process environment to the attacker.
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-shared-infrastructure (version 40.14.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/pladddform-shared-infrastructure across your stack and pipelines.
If you installed it — respond
@hrmony/pladddform-shared-infrastructure 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-shared-infrastructure 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-shared-infrastructure 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-shared-infrastructure-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.