# MAL-2026-17253: Malicious code in @hrmony/benefit-essenszuschuss (npm)


- **Type:** Malicious package
- **Package:** `@hrmony/benefit-essenszuschuss` (npm)
- **Published:** 29 Sep 2026
- **Also known as:** GHSA-2c72-pm8g-m65j

## What is MAL-2026-17253?

MAL-2026-17253 is a malicious package in @hrmony/benefit-essenszuschuss, published on 29 Sep 2026. 

### Official description

On module import, top-level code in this package harvests cloud and container secrets and posts them to a hardcoded attacker-controlled endpoint. It queries the AWS Instance Metadata Service (IMDSv2 token via PUT to /latest/api/token, then /iam/security-credentials/ and identity-credentials/ec2) to retrieve IAM role credentials, serializes the full process.env, and recursively reads /var/run/secrets/ to capture Kubernetes service-account tokens and mounted secret material. The collected data is POSTed as JSON to https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_benefit-essenszuschuss. The package name mimics an internal @hrmony HR/benefits utility, consistent with a dependency-confusion payload targeting that scope; it also declares an unpinned dependency @hrmony/kit-5 (^1.0.0) that will be resolved from the public registry at install time.

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-17253?

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-17253 is a malicious package: @hrmony/benefit-essenszuschuss (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-17253/ (Markdown: https://insights.sbomify.com/MAL-2026-17253/index.md)
```

## Sources

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

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