# MAL-2026-5460: Malicious code in fhirproxy (npm)


- **Type:** Malicious package
- **Package:** `fhirproxy` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-g7wh-3cfq-x8m2

## What is MAL-2026-5460?

MAL-2026-5460 is a malicious package in fhirproxy, published on 9 Jun 2026. 

### Official description

fhirproxy@90.0.0 is a thin loader package whose only behavior is to pull and execute the dependency `fhirproxy-utils`. package.json declares both `preinstall` and `postinstall` hooks that run `node index.js`, and index.js's only meaningful statement is `require('fhirproxy-utils')`. That dependency is fetched from npm at install time and its top-level code runs on the installer's machine during `npm install` without further user interaction. The package additionally claims a `bin` map that aliases the names of widely used developer tools — `webpack`, `webpackcli`, `vite`, `eslint`, `jest`, `tsc`, `tsnode`, `prettier`, `next`, `nodemon`, `turbo` — all pointing at the same `index.js`. Once installed, `node_modules/.bin/<tool>` resolves to this package, so any subsequent invocation of those commands in the project (CI builds, local dev scripts) re-executes index.js and re-loads fhirproxy-utils instead of the genuine tool. The package presents itself as OpenMRS REST tooling (`author: "OpenMRS Community Contributor"`, version 90.0.0, 351-byte stub printing `[+] OpenMRS REST Utilities Subsystem Initialized.`), but real OpenMRS packages are scoped under `@openmrs/*` and published by named maintainers — this is impersonation, not a real OpenMRS project. The combination of impersonation metadata, lifecycle-hook execution of an opaque dependency, and bin-hijacking of common dev tooling forces installer-side execution of attacker-controlled code at install time and on every subsequent invocation of any hijacked tool name.

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

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-5460 is a malicious package: fhirproxy (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-5460/ (Markdown: https://insights.sbomify.com/MAL-2026-5460/index.md)
```

## Sources

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

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