Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malware in gifuct

The npm package gifuct was found to contain malware, resulting in full system compromise of any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.

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

The npm package gifuct was identified as containing malware. According to the GitHub Advisory (GHSA-829c-v26f-5g9m), any computer that has this package installed or running should be considered fully compromised.\n\nAffected systems require immediate remediation. All secrets and cryptographic keys stored on compromised computers should be rotated immediately from a different, unaffected computer. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis is a critical supply chain incident affecting the npm ecosystem.

Indicators of compromise

Packages
  • gifuct

Remediation

  • Immediately rotate all secrets and cryptographic keys from a different, unaffected computer
  • Remove the gifuct package from all affected systems
  • Conduct a full security audit of any system that had gifuct installed
  • Monitor affected systems for signs of unauthorized access or persistence mechanisms
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved

Sources

  1. GitHub Advisory GHSA-829c-v26f-5g9m · GitHub Advisory Database

Cite this entry

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

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