Malware in fhirproxy-utils
Malware was discovered in the npm package fhirproxy-utils, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately, and the package should be removed.
- Disclosed
- Last updated
- Blast radius
- Any system with fhirproxy-utils installed or running
- Ecosystems
- Attack vectors
- Affected entities
- fhirproxy-utils
A critical malware incident was identified in the npm package fhirproxy-utils. According to the GitHub Advisory (GHSA-cw9q-6cmp-p38r), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a severe supply chain attack through a compromised npm package with potential for widespread impact across all systems that have installed or executed the affected package.
Indicators of compromise
- Packages
- fhirproxy-utils
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the fhirproxy-utils package from all affected systems
- Conduct a full security audit of any system that had fhirproxy-utils installed
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Consider full system reimaging if the package was installed on critical infrastructure
- Review access logs and audit trails for any suspicious activity during the period the package was installed
Sources
- GitHub Advisory GHSA-cw9q-6cmp-p38r · GitHub Advisory Database
Cite this entry
"Malware in fhirproxy-utils." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 15, 2026; last updated July 15, 2026. https://supplychainattack.org/incident/malware-in-fhirproxy-utils-1v3nsy
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package