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

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

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

@hrmony/pladddform-codegen 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-codegen — how do I know if it already compromised me?

If @hrmony/pladddform-codegen 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-codegen part of a known attack campaign?

Yes — @hrmony/pladddform-codegen is associated with the IN-MAL-2026-020650 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-codegen 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-codegen (version 49.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/pladddform-codegen across your stack and pipelines.

Malicious package

@hrmony/pladddform-codegennpm

@hrmony/pladddform-codegen is a confirmed malicious npm package (MAL-2026-17273) that steals credentials and exfiltrates sensitive data (malicious version 49.99.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @hrmony/pladddform-codegen (npm)

MAL-2026-17273

Immediate action

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

npm uninstall @hrmony/pladddform-codegen

What this malware does

On module load, index.js unconditionally beacons to the hardcoded non-first-party endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-codegen and then performs three credential-harvest flows against the installer: (1) queries the AWS instance metadata service at 169.254.169.254 (IMDSv2), enumerates IAM role names, retrieves each role's security credentials, and collects the EC2 identity document, user-data, and network-interface metadata; (2) enumerates all process.env entries; (3) recursively reads /var/run/secrets/ (Kubernetes projected service-account tokens and mounted secrets). The collected data is POSTed to the same hardcoded attacker host. The package name is a typosquat of an @hrmony scoped package with an inflated version (49.99.0) consistent with a dependency-confusion attempt, and it declares an internal-looking sibling dependency @hrmony/kit-5. The exfiltration URL path embeds the package name, indicating a campaign-style beacon per lure.

Malicious versions

1 flagged

49.99.0

Indicators of compromise (SHA-256)

58f0706d7223f8a1ff87ac80c6e1e42af148214545e55acc865cce12fee7eec4

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-codegen (version 49.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/pladddform-codegen across your stack and pipelines.
If you installed it — respond
@hrmony/pladddform-codegen 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-codegen 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-codegen 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-codegen on npm has been identified as a malicious package (version 49.99.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020650

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @hrmony/pladddform-codegen-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