NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @hrmony published 34 malicious packages. See the full campaign →
Malicious package

@hrmony/pladddform-partner-registrynpm

Advisory published Updated

@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)

MAL-2026-17278
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @hrmony/pladddform-partner-registry

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.

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

1 flagged
40.14.3

Indicators of compromise (SHA-256)

e09dd7e6a7777c82ec319c374c862db40d6bf7210991dac9a7a250fda4a259e7
f8d38fe19118aa47b618021ff16cbe489dd597f9a0b7f3ad8a1024676ab505b6

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @hrmony/pladddform-partner-registry (version 40.14.3).

  2. 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.

  3. Did it already run?

    If @hrmony/pladddform-partner-registry was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @hrmony/pladddform-partner-registry on npm has been identified as a malicious package (version 40.14.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020645GHSA-757q-42rv-qjcf

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.

Explore

@hrmony/pladddform-partner-registry (npm) malicious package — MAL-2026-17278 | O3 Security