Malware in @jagreehal/workflow
Malware in @jagreehal/workflow Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to a
- Disclosed
- Last updated
- Blast radius
- npm package(s): @jagreehal/workflow
- Ecosystems
- Attack vectors
- Threat actor
- Affected entities
- @jagreehal/workflow
Malware in @jagreehal/workflow Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to a
This entry was assembled automatically from a public advisory and reflects the source at ingestion time. See the cited sources for authoritative detail.
Indicators of compromise
- Packages
- @jagreehal/workflow
Remediation
- Remove @jagreehal/workflow from all dependency trees and lockfiles.
- Rotate any credentials present on machines or CI that installed the package.
- Pin and verify dependencies; restrict install scripts (e.g. --ignore-scripts).
Sources
- GitHub Advisory GHSA-6w7v-23mf-65g3 · GitHub Advisory Database
- Miasma v2: Self-Spreading npm Worm Now Uses Malicious binding.gyp file and Compromises 57 Packages | Semgrep · Semgrep
Cite this entry
"Malware in @jagreehal/workflow." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 4, 2026; last updated June 6, 2026. https://supplychainattack.org/incident/malware-in-jagreehal-workflow-g838pk
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in chain-manager
Malware discovered in the npm package chain-manager. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malicious code in @finxsecdemo/utils (npm)
The npm package @finxsecdemo/utils version 1.0.2 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity.
npmCompromised package - containedcritical
Malware in @bowozzz/baileys
The npm package @bowozzz/baileys contained malware that grants full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
npmCompromised package - containedcritical
Malicious code in blots (npm)
The npm package 'blots' version 2.1.0 was identified by the OpenSSF Package Analysis project as containing malicious code that executes commands associated with malicious behavior. The package has been flagged in the OpenSSF malicious packages database.
npmCompromised package