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. resolvedcritical

    Malicious code in autbank-core (npm)

    The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.

    npmCompromised package
  2. resolvedcritical

    Malicious code in adxaa (npm)

    The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.

    npmCompromised package
  3. resolvedcritical

    Malicious code in upload-to-gcp (npm)

    upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.

    npmCompromised package
  4. resolvedcritical

    Malicious code in akamai-sensor (npm)

    A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.

    npmCompromised packageTyposquatting