Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in poly-kelly

Malware was discovered in the npm package poly-kelly. The package grants full system compromise to attackers and should be considered a critical threat to any system where it is installed or running.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • poly-kelly

A malware-laden version of the npm package poly-kelly was identified and published via GitHub Advisory GHSA-c37j-v3j2-6gf8. The package contains malicious code that provides attackers with full control of any computer on which it is installed or executed.\n\nSystems with poly-kelly installed should be considered fully compromised. All secrets, keys, and credentials stored on affected machines must be rotated immediately from a separate, uncompromised computer. While the package can be removed, complete remediation is not guaranteed due to the potential for additional malicious software to have been deployed during the compromise.\n\nThe advisory was published on 2026-07-29 via the GitHub Advisory Database.

Indicators of compromise

Packages
  • poly-kelly

Remediation

  • Immediately remove the poly-kelly package from all systems
  • Rotate all secrets, keys, and credentials from a separate, uncompromised computer
  • Perform a full security audit and malware scan of affected systems
  • Monitor affected systems for signs of unauthorized access or persistence mechanisms
  • Review system logs for suspicious activity during the period the package was installed

Sources

  1. GitHub Advisory GHSA-c37j-v3j2-6gf8 · GitHub Advisory Database

Cite this entry

"Malware in poly-kelly." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 29, 2026; last updated July 29, 2026. https://supplychainattack.org/incident/malware-in-poly-kelly-10t83s

Suggest a correction

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

  1. containedcritical

    Malware in polymarket-risk-manager

    Malware was discovered in the npm package polymarket-risk-manager, potentially providing full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package
  2. containedcritical

    Malicious code in toll_free (npm)

    The npm package toll_free version 1.0.1 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.

    npmCompromised package
  3. 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
  4. 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