Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in rabi-snooze-api

Malware discovered in the npm package rabi-snooze-api. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from unaffected systems.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • rabi-snooze-api

A malware-laden version of the npm package rabi-snooze-api has been identified and published to the npm registry. The malicious package provides attackers with full control over any system on which it is installed or executed.\n\nAny computer running this package should be considered fully compromised. All secrets, keys, and credentials stored on affected systems must be rotated immediately from a different, unaffected computer. While the package should be removed, complete remediation cannot be guaranteed due to the potential for additional malicious software to have been installed during the compromise.\n\nThe advisory was published on 2026-07-09 via GitHub Security Advisory GHSA-cpfq-7jvh-rc7w.

Indicators of compromise

Packages
  • rabi-snooze-api

Remediation

  • Immediately remove the rabi-snooze-api package from all systems
  • Rotate all secrets, keys, and credentials from a clean, unaffected computer
  • Perform a full security audit and malware scan of any affected systems
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider rebuilding affected systems from clean media if full compromise is suspected

Sources

  1. GitHub Advisory GHSA-cpfq-7jvh-rc7w · GitHub Advisory Database

Cite this entry

"Malware in rabi-snooze-api." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 9, 2026; last updated July 9, 2026. https://supplychainattack.org/incident/malware-in-rabi-snooze-api-03k5hn

Suggest a correction

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

  1. containedcritical

    Malware in myclaude-code

    Malware was discovered in the npm package myclaude-code. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.

    npmCompromised package
  2. resolvedcritical

    Malware in clavue

    The npm package clavue contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package
  3. containedcritical

    Malware in airkey-mfa-react

    Malware was discovered in the npm package airkey-mfa-react. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different computer.

    npmCompromised package
  4. resolvedcritical

    Malware in fusion-client

    The npm package fusion-client contained malware that provided full system compromise to attackers. Any computer with the package installed should be considered fully compromised and all secrets and keys rotated from a different machine.

    npmCompromised package