Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in @amiga-fwk-nodejs/metrics (npm)

The npm package @amiga-fwk-nodejs/metrics was found to contain malicious code. The package has been identified and reported by the OpenSSF malicious packages project.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Unknown; depends on adoption of affected versions
Ecosystems
Attack vectors
Affected entities
  • @amiga-fwk-nodejs/metrics

The npm package @amiga-fwk-nodejs/metrics was discovered to contain malicious code. The vulnerability was identified and credited to the OpenSSF's malicious packages initiative, which maintains a public catalog of known malicious packages across package ecosystems.\n\nThe malicious package was published to npm and could affect any project that installed or depended on @amiga-fwk-nodejs/metrics. The OpenSSF advisory (GHSA-g8h2-q3c5-hcm7) documents the finding with reference to the malicious packages repository.\n\nNo specific technical details about the malicious payload or its behavior are provided in the source material.

Indicators of compromise

Packages
  • @amiga-fwk-nodejs/metrics

Remediation

  • Remove @amiga-fwk-nodejs/metrics from all projects and dependencies
  • Audit project dependencies for any other suspicious or unknown packages
  • Review package.json and lock files for unexpected entries
  • Consider using npm audit and security scanning tools to identify other potentially compromised dependencies
  • If the package was installed, review system logs and process execution for signs of compromise

Sources

  1. GitHub Advisory GHSA-g8h2-q3c5-hcm7 · GitHub Advisory Database

Cite this entry

"Malicious code in @amiga-fwk-nodejs/metrics (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 26, 2026; last updated July 26, 2026. https://supplychainattack.org/incident/malicious-code-in-amiga-fwk-nodejs-metrics-npm-1jkchb

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