Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in rma-utils

Malware was discovered in the npm package rma-utils, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a clean system.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with rma-utils installed or running
Ecosystems
Attack vectors
Affected entities
  • rma-utils

A critical malware incident was identified in the npm package rma-utils. According to the GitHub Advisory (GHSA-c633-xc97-ch23), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThe severity is critical due to the potential for complete system takeover and the difficulty in ensuring full remediation once the malware has executed.

Indicators of compromise

Packages
  • rma-utils

Remediation

  • Immediately remove the rma-utils package from all affected systems
  • Rotate all secrets, API keys, credentials, and authentication tokens from a clean, uncompromised computer
  • Assume full system compromise and conduct a thorough security audit of affected machines
  • Consider reimaging or replacing affected systems if possible
  • Monitor for any signs of persistent malware or unauthorized access following removal

Sources

  1. GitHub Advisory GHSA-c633-xc97-ch23 · GitHub Advisory Database

Cite this entry

"Malware in rma-utils." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-rma-utils-hde5x3

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 typescirpt-cli (npm)

    The npm package typescirpt-cli (a typosquat of typescript-cli) contained malicious code in its postinstall script that downloads and executes a binary (main.exe) on Windows and WSL systems, and exfiltrates system metadata to a hardcoded IP address.

    npmTyposquattingCompromised package
  2. containedcritical

    Malicious code in typescipt-core (npm)

    The npm package typescipt-core (a typosquat of typescript) contained malicious postinstall code that downloads and executes a second-stage payload on Windows and WSL systems. The dropper exfiltrates host profile information to 193.70.34.101:20099 before fetching attacker-controlled executables.

    npmCompromised packageTyposquatting
  3. containedcritical

    Malicious code in typesript-cli (npm)

    The npm package 'typesript-cli' (a one-character typosquat of 'typescript') contains malicious code in its postinstall script that downloads and executes a Windows PE binary, and can cross the Linux/WSL sandbox boundary to execute payloads on the Windows host. The script also beacons to a hardcoded IP endpoint.

    npmTyposquattingCompromised package
  4. resolvedcritical

    Malicious code in @mohamed_nowisar/depconf-canary-test (npm)

    The npm package @mohamed_nowisar/depconf-canary-test contained malicious code in its preinstall hook that automatically collected and exfiltrated host and CI environment information to an attacker-controlled webhook endpoint without user consent.

    npmCompromised package