Malware in @kl-dolphin/swim
Malware was discovered in the npm package @kl-dolphin/swim, resulting in full system compromise of any computer with the package installed or running. The advisory recommends immediate removal of the package and rotation of all secrets and keys from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @kl-dolphin/swim
A malware incident was identified in the npm package @kl-dolphin/swim, published as GitHub Advisory GHSA-rr7c-77w4-j8c8 on June 24, 2026.\n\nAccording to the advisory, any computer with this package installed or running should be considered fully compromised. The malware grants outside entities full control of affected systems.\n\nImmediate remediation steps include removing the package and rotating all secrets and keys from a different, unaffected computer. However, the advisory notes that removal of the package may not eliminate all malicious software that resulted from the installation, given the level of system compromise.\n\nUsers should assume complete loss of confidentiality and integrity on any system where this package was present.
Indicators of compromise
- Packages
- @kl-dolphin/swim
Remediation
- Remove the @kl-dolphin/swim package immediately from all systems
- Rotate all secrets, keys, and credentials from a different, unaffected computer
- Assume full system compromise and conduct forensic analysis
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider rebuilding affected systems from clean media if possible
Sources
- GitHub Advisory GHSA-rr7c-77w4-j8c8 · GitHub Advisory Database
Cite this entry
"Malware in @kl-dolphin/swim." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 24, 2026; last updated June 24, 2026. https://supplychainattack.org/incident/malware-in-kl-dolphin-swim-1eddrh
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- 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 - 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 - 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 - 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