Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in @amber-team/figma-utils (npm)

The npm package @amber-team/figma-utils was found to contain malicious code. The package was identified by the OpenSSF malicious-packages project and reported via GitHub Advisory GHSA-2j44-84pc-388j.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Unknown; depends on adoption of affected versions
Ecosystems
npm
Attack vectors
Compromised package
Affected entities
  • @amber-team/figma-utils

The npm package @amber-team/figma-utils was discovered to contain malicious code. The malicious package was identified and documented by the OpenSSF's malicious-packages project, which maintains a catalog of known malicious software supply chain incidents.\n\nThe advisory was published on 2026-07-26 and assigned GitHub Advisory identifier GHSA-2j44-84pc-388j. The OpenSSF credited the discovery and classification of this incident.\n\nAny projects that depend on @amber-team/figma-utils should audit their usage and remove or update to a clean version if available.

Indicators of compromise

Packages
  • @amber-team/figma-utils

Remediation

  • Identify all projects and dependencies using @amber-team/figma-utils
  • Remove the package or update to a verified clean version if available
  • Audit systems that may have executed code from affected versions for signs of compromise
  • Review npm package.json and lock files for this dependency
  • Consider using npm audit or similar tools to detect the malicious package in your supply chain

Sources

  1. GitHub Advisory GHSA-2j44-84pc-388j · GitHub Advisory Database

Cite this entry

"Malicious code in @amber-team/figma-utils (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 26, 2026; last updated July 26, 2026. https://supplychainattack.org/incident/malicious-code-in-amber-team-figma-utils-npm-15zzof

Suggest a correction

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

Related incidents

  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