Which versions of @hrmony/cdk-constructs are malicious?

The following npm versions of @hrmony/cdk-constructs are flagged malicious: 5.3.5. Treat any of these as compromised.

How do I remediate @hrmony/cdk-constructs if I installed it?

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

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

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

Malicious package

@hrmony/cdk-constructsnpm

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

Malicious code in @hrmony/cdk-constructs (npm)

MAL-2026-17258

Immediate action

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

npm uninstall @hrmony/cdk-constructs

What this malware does

On require/import, index.js executes top-level async code that harvests AWS EC2 instance metadata via IMDSv2 (including IAM role security credentials fetched from http://169.254.169.254/latest/meta-data/iam/security-credentials/), serializes the entire process.env, and recursively reads files under /var/run/secrets/ (Kubernetes service account tokens and mounted secrets). The collected data is POSTed as JSON to a hardcoded external endpoint at https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_cdk-constructs. The package name uses the scope @hrmony, a one-character deletion of the @harmony scope, consistent with typosquat targeting of developers looking for AWS CDK constructs. package.json also declares a runtime dependency on @hrmony/kit-5 at ^1.0.0, an unpinned scoped package under the same attacker-controlled scope, resolved and installed alongside this package.

Malicious versions

1 flagged

5.3.5

Indicators of compromise (SHA-256)

6601c44353f60d117ef4e1ea09f9d2c997cde4375af70c49c628b38db8f1b55a

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

Campaign

IN-MAL-2026-020659

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @hrmony/cdk-constructs-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