@hrmony/pladddform-partner-registrynpm
@hrmony/pladddform-partner-registry is a confirmed malicious npm package (MAL-2026-17278) 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-partner-registry (npm)
What this malware does
On import, index.js executes a top-level fetch that harvests cloud and container secrets from the installer host and POSTs them to the hardcoded attacker endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-partner-registry. The collection code queries the AWS EC2 Instance Metadata Service at 169.254.169.254 using IMDSv2, enumerates IAM role names under /iam/security-credentials/, fetches the temporary IAM security credentials, the instance identity document, and EC2 user-data, enumerates every entry of process.env, and recursively reads all files under /var/run/secrets/ (Kubernetes service-account tokens and mounted secrets). The collected payload is serialized as JSON and sent to the attacker-controlled host. The package name uses a typo-shape ('pladddform') under the @hrmony scope and declares a dependency on a sibling '@hrmony/kit-5', consistent with a coordinated typosquat/dependency-confusion campaign. The package provides no legitimate functionality; its sole on-import effect is credential and secret exfiltration.
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-partner-registry (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-partner-registry across your stack and pipelines.
If you installed it — respond
@hrmony/pladddform-partner-registry 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-partner-registry 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-partner-registry 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-partner-registry-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.