Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in @amber-team/react-modal-stack (npm)

The npm package @amber-team/react-modal-stack was found to contain malicious code. The package was identified by the OpenSSF malicious-packages project and reported via GitHub Security Advisory GHSA-44rm-8vq6-qhf5.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Unknown; depends on adoption of affected versions
Ecosystems
Attack vectors
Affected entities
  • @amber-team/react-modal-stack

The npm package @amber-team/react-modal-stack was identified as containing malicious code. The discovery was credited to the OpenSSF's malicious-packages project, which maintains a catalog of known malicious packages across package ecosystems.\n\nThe advisory was published on GitHub as GHSA-44rm-8vq6-qhf5 and tracked in the OpenSSF malicious-packages repository under identifier MAL-2025-7065. The specific nature of the malicious payload and affected versions are not detailed in the source text.\n\nThis incident represents a direct compromise of the package distribution, where malicious code was introduced into the published npm package itself.

Indicators of compromise

Packages
  • @amber-team/react-modal-stack

Remediation

  • Remove @amber-team/react-modal-stack from all projects and dependencies
  • Audit project dependencies for any use of this package
  • Review any systems that may have installed this package for signs of compromise
  • Use npm audit to identify affected installations
  • Replace with a legitimate alternative for modal stack functionality

Sources

  1. GitHub Advisory GHSA-44rm-8vq6-qhf5 · GitHub Advisory Database

Cite this entry

"Malicious code in @amber-team/react-modal-stack (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-react-modal-stack-npm-1h6ort

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 @aligntech-cw/alignerfit (npm)

    Malicious code was discovered in the npm package @aligntech-cw/alignerfit. The package was identified by the OpenSSF malicious-packages project and assigned identifier MAL-2024-1743.

    npmCompromised package
  2. resolvedcritical

    Malicious code in @akunsansan0/susu10 (npm)

    @akunsansan0/susu10 is a malicious npm package containing autopublish scripts designed to automatically generate and republish derivative packages with randomized names to the npm registry. The package was part of a tea.xyz token reward campaign that flooded npm with similar malicious packages.

    npmCompromised package
  3. containedcritical

    Malicious code in @antv/f-wx (npm)

    The npm account `atool` was compromised and used to publish 631 malicious versions across 314 packages, including @antv/f-wx. Each version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials via the GitHub API and establishes persistence through CI/CD workflow injection and system daemons.

    Mini Shai HuludTeamPCPnpmOtherAccount takeoverCompromised packageMalicious commit
  4. resolvedcritical

    Malicious code in @akunsansan0/susu11 (npm)

    @akunsansan0/susu11 is a malicious npm package containing autopublish scripts designed to automatically generate and republish derivative packages with randomized names to inflate tea protocol token rewards. The package modifies package.json, changes version numbers, and continuously pollutes the npm registry with variants.

    npmCompromised package