Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in procwire

Malware was discovered in the npm package procwire, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a different computer.

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

A critical malware incident was identified in the npm package procwire. According to the GitHub Advisory (GHSA-5r42-357x-f2mx), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate removal of the package and rotation of all secrets and keys from a different, unaffected computer. However, due to the nature of the compromise, there is no guarantee that removing the package will eliminate all malicious software that may have been installed as a result.\n\nThis represents a severe supply chain attack through a compromised npm package with potential for widespread impact across all systems that installed or executed the affected code.

Indicators of compromise

Packages
  • procwire

Remediation

  • Immediately remove the procwire package from all affected systems
  • Rotate all secrets, keys, and credentials from a different, unaffected computer
  • Assume full system compromise and conduct forensic analysis
  • Review system logs for unauthorized access or activity
  • Consider full system reimaging if critical infrastructure is affected
  • Monitor for any lateral movement or persistence mechanisms

Sources

  1. GitHub Advisory GHSA-5r42-357x-f2mx · GitHub Advisory Database

Cite this entry

"Malware in procwire." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-procwire-sfo4ra

Suggest a correction

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

  1. containedcritical

    Malware in awaitly-libsql

    The npm package awaitly-libsql was found to contain malware. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.

    npmCompromised package
  2. containedcritical

    Malware in autotel-mcp-instrumentation

    Malware was discovered in the npm package autotel-mcp-instrumentation. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.

    npmCompromised package
  3. activecritical

    Malware in autotel-pact

    The npm package autotel-pact contains malware that grants full control of affected systems to an outside entity. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package
  4. containedcritical

    Malware in autotel-playwright

    Malware was discovered in the npm package autotel-playwright. Systems with this package installed or running are considered fully compromised and require immediate remediation.

    npmCompromised package