Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in syco1

Malware was discovered in the npm package syco1, resulting in full system compromise for any computer with the package installed or running. All affected systems should be considered fully compromised and all secrets and keys rotated immediately from a different computer.

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

The npm package syco1 was found to contain malware. According to the GitHub Advisory (GHSA-9mh8-xw8w-jh9g), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated immediately from a different, unaffected computer. 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\nThe advisory was published on 2026-07-07 via the GitHub Advisory database.

Indicators of compromise

Packages
  • syco1

Remediation

  • Immediately rotate all secrets and keys stored on affected computers from a different, unaffected computer
  • Remove the syco1 package from all affected systems
  • Perform a full security audit and malware scan on any system that had syco1 installed
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
  • Review access logs and monitor for unauthorized activity on affected systems

Sources

  1. GitHub Advisory GHSA-9mh8-xw8w-jh9g · GitHub Advisory Database

Cite this entry

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

Suggest a correction

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

  1. 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
  2. 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
  3. 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
  4. 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