Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

fhirproxynpm

Malicious code in fhirproxy (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5460
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall fhirproxy

What this malware does

[email protected] 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.

Malicious versions

1 flagged
90.0.0

Indicators of compromise (SHA-256)

96e092973bad8e995bdec34000e45943e0be59996e84f181ee4bee9cd423f8eb
f10d16da1fb5b7ed2d0dc07f015466cee8f7b2ba9c118ac7c6989c717ac3dd62

Frequently asked questions

No. fhirproxy on npm has been identified as a malicious package (version 90.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005165IN-MAL-2026-005166

References

Credits

  • Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection
fhirproxy (npm) malicious package — MAL-2026-5460 | O3 Security