# MAL-2026-17258: Malicious code in @hrmony/cdk-constructs (npm)


- **Type:** Malicious package
- **Package:** `@hrmony/cdk-constructs` (npm)
- **Published:** 29 Sep 2026
- **Also known as:** GHSA-h9qw-wcm3-qrr8

## What is MAL-2026-17258?

MAL-2026-17258 is a malicious package in @hrmony/cdk-constructs, published on 29 Sep 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-17258?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17258 is a malicious package: @hrmony/cdk-constructs (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17258/ (Markdown: https://insights.sbomify.com/MAL-2026-17258/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17258

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17258/
Summaries are generated and may contain mistakes; the official description above is the record.