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

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

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

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

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

Yes — @hrmony/pladddform-testing is associated with the IN-MAL-2026-020643 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-testing 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-testing (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-testing across your stack and pipelines.

Malicious package

@hrmony/pladddform-testingnpm

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

MAL-2026-17280

Immediate action

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

npm uninstall @hrmony/pladddform-testing

What this malware does

On module import, index.js executes an unconditional exfiltration payload against the installer/runtime host. It queries the AWS EC2 Instance Metadata Service at http://169.254.169.254 using IMDSv2 to enumerate the instance identity document, user-data, IAM role names, and the per-role temporary security credentials. It also enumerates every entry of process.env and recursively reads all files under /var/run/secrets/ (the standard Kubernetes service-account and secret mount). The combined data is POSTed to the hardcoded attacker endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-testing, and a separate top-level fetch to the same host beacons successful execution. The package ships no legitimate functionality: its only substantive file is the exfil script, the description is empty, and the name (@hrmony/pladddform-testing) plus the exfil URL path segment (pkge_hrmony_pladddform-testing) match a typosquat/dependency-confusion shape targeting an internal or similarly named scope.

Malicious versions

1 flagged

40.14.3

Indicators of compromise (SHA-256)

607004ff93f1fcd5fbf7b1cf6b5e104b7f26eb699aee3dd4f8bbb33494f0b096

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-testing (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-testing across your stack and pipelines.
If you installed it — respond
@hrmony/pladddform-testing 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-testing 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-testing 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-testing 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-020643

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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