Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in fhirproxy

Malware was discovered in the fhirproxy npm package. Systems with the package installed or running are considered fully compromised, with potential for complete system takeover.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with fhirproxy installed or running
Ecosystems
Attack vectors
Affected entities
  • fhirproxy

The fhirproxy npm package was found to contain malware. According to the GitHub Advisory (GHSA-g7wh-3cfq-x8m2), 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, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThe full scope of the malware's capabilities and the extent of its distribution remain under investigation.

Indicators of compromise

Packages
  • fhirproxy

Remediation

  • Immediately isolate any system with fhirproxy installed from the network
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the fhirproxy package from all affected systems
  • Conduct a full forensic analysis of affected systems to identify any additional malicious software
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved

Sources

  1. GitHub Advisory GHSA-g7wh-3cfq-x8m2 · GitHub Advisory Database

Cite this entry

"Malware in fhirproxy." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 15, 2026; last updated July 15, 2026. https://supplychainattack.org/incident/malware-in-fhirproxy-l4owwi

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedcritical

    Malware in @hkyyy/portal-widget-helper-0601

    Malware was discovered in the npm package @hkyyy/portal-widget-helper-0601. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  2. resolvedcritical

    Malware in @saladin0x1/js-shared-modules

    Malware was discovered in the npm package @saladin0x1/js-shared-modules. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  3. containedcritical

    Malware in js-shared-modules

    Malware was discovered in the npm package js-shared-modules. Systems with this package installed or running are considered fully compromised, with potential for complete system takeover.

    npmCompromised package
  4. activecritical

    Malware in patientdocuments

    The npm package patientdocuments contains malware that grants full system compromise to an outside entity. Any computer with this package installed or running should be considered fully compromised and all secrets and keys should be rotated immediately from a different computer.

    npmCompromised package