Which versions of @hrmony/pladddform-cli are malicious?

The following npm versions of @hrmony/pladddform-cli are flagged malicious: 40.14.3. Treat any of these as compromised.

How do I remediate @hrmony/pladddform-cli if I installed it?

@hrmony/pladddform-cli 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.

I already installed @hrmony/pladddform-cli — how do I know if it already compromised me?

If @hrmony/pladddform-cli 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.

Is @hrmony/pladddform-cli part of a known attack campaign?

Yes — @hrmony/pladddform-cli is associated with the IN-MAL-2026-020648 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @hrmony/pladddform-cli across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @hrmony/pladddform-cli (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-cli across your stack and pipelines.

Malicious package

@hrmony/pladddform-clinpm

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

MAL-2026-17272

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @hrmony/pladddform-cli

What this malware does

On require/import, index.js performs three attacker-benefiting actions against a hardcoded endpoint at https://hrnmn.dd.h4x.tv/. First, it POSTs an unconditional install/import beacon ({'c53':'hello'}) to that host. Second, aws_get() contacts the EC2 Instance Metadata Service at 169.254.169.254, obtains an IMDSv2 token, enumerates IAM roles under /iam/security-credentials/, and retrieves each role's temporary AWS credentials along with user-data and the instance identity document, then POSTs them to the same host. Third, local_get() enumerates every entry in process.env and recursively reads files under /var/run/secrets/ (Kubernetes service-account tokens and mounted secrets) and POSTs the aggregated dump to the same host. The destination domain is unrelated to any AWS, Kubernetes, or legitimate telemetry provider, and the exfiltrated material (IAM instance-role STS credentials, environment variables, and Kubernetes secret material) enables immediate cloud-account and cluster takeover. The package name '@hrmony/pladddform-cli' also resembles a legitimate 'harmony/platform-cli' identifier with letter alterations consistent with typosquatting.

Malicious versions

1 flagged

40.14.3

Indicators of compromise (SHA-256)

81b9c27ba35a6978a0731d77b7d5fec367f4c2a8b4acc5838588071c89886fa4

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @hrmony/pladddform-cli (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-cli across your stack and pipelines.
If you installed it — respond
@hrmony/pladddform-cli 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-cli 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-cli 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

No. @hrmony/pladddform-cli 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-020648

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @hrmony/pladddform-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database