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-confignpm

Advisory published Updated

@hrmony/pladddform-config is a confirmed malicious npm package (MAL-2026-17274) 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-config (npm)

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

What this malware does

index.js executes at module top level on require/import. It performs an unconditional POST check-in to https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-config, then runs three collection routines and exfiltrates their output to the same host. aws_get() requests an IMDSv2 token from 169.254.169.254, enumerates the EC2 instance identity document and IAM roles, and fetches temporary AWS credentials from /iam/security-credentials/<role>. local_get() serializes the entire process.env and recursively reads all files under /var/run/secrets/, which on Kubernetes contains mounted service-account tokens and other secrets. Each result is POSTed as JSON to the hardcoded EXPORTER_URL at hrnmn.dd.h4x.tv. The package ships no advertised functionality, has an empty description, and its scope/name (@hrmony/pladddform-config) and declared dependency (@hrmony/kit-5) use a lookalike internal-scope shape consistent with dependency-confusion targeting.

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)

2de81847796671c2a5e9f97a94fae50352b0dff0816e4f0a7dfaf707fbb92629
4e9c92a357bb0f065c93c6370e90faebf15aa3ed8ed1c4570dab1a0fe73fc330

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    @hrmony/pladddform-config 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-config 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-config 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-020649GHSA-pgw6-px39-j8m8

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @hrmony/pladddform-config-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-config (npm) malicious package — MAL-2026-17274 | O3 Security