Malware in po-ops-local-dev
The npm package po-ops-local-dev was found to contain malware, resulting in full system compromise of any computer with the package installed or running. GitHub Security Advisory GHSA-r7j7-4gwg-rg72 was published on 2026-07-10.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- po-ops-local-dev
The npm package po-ops-local-dev has been identified as containing malware. According to the GitHub Security Advisory, any computer that has 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 package installation, given that the outside entity may have gained full control of the system.\n\nAffected users should treat any system that has run this package as potentially fully compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- po-ops-local-dev
Remediation
- Remove the po-ops-local-dev package immediately
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Assume full system compromise and perform forensic analysis or rebuild affected systems
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Monitor for any unauthorized activity on accounts or systems that may have been accessed from the compromised machine
Sources
- GitHub Advisory GHSA-r7j7-4gwg-rg72 · GitHub Advisory Database
Cite this entry
"Malware in po-ops-local-dev." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 10, 2026; last updated July 10, 2026. https://supplychainattack.org/incident/malware-in-po-ops-local-dev-1i2pwx
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 test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, 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 from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package