Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in svelte-kit-streak

Malware was discovered in the npm package svelte-kit-streak. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • svelte-kit-streak

The npm package svelte-kit-streak was found to contain malware. According to the GitHub Advisory (GHSA-rc4p-g2mc-7w8h), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. The package should be removed, though there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for complete system takeover."

Indicators of compromise

Packages
  • svelte-kit-streak

Remediation

  • Immediately remove the svelte-kit-streak package from all affected systems
  • Rotate all secrets, API keys, and credentials from a clean, uncompromised computer
  • Assume full system compromise and conduct forensic analysis to identify any additional malicious software
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Notify all users and systems that may have installed this package

Sources

  1. GitHub Advisory GHSA-rc4p-g2mc-7w8h · GitHub Advisory Database

Cite this entry

"Malware in svelte-kit-streak." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 10, 2026; last updated August 10, 2026. https://supplychainattack.org/incident/malware-in-svelte-kit-streak-fsvts3

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