Malware in @kl-dolphin/jump
Malware was discovered in the npm package @kl-dolphin/jump, 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/jump
A malware-laden version of the npm package @kl-dolphin/jump was identified and published on GitHub's advisory database (GHSA-wfwr-cf4w-fpj5). The package grants full control of the affected system to an outside entity upon installation or execution.\n\nAccording to the advisory, any computer with this package installed or running should be considered fully compromised. All secrets, keys, and credentials stored on affected systems should be rotated immediately from a different, uncompromised computer.\n\nWhile removal of the package is recommended, the advisory notes that full system compromise may have occurred, meaning removal of the package alone may not eliminate all malicious software that was installed as a result of the initial compromise.\n\nThe package should be avoided entirely, and users should verify their systems for any signs of compromise or unauthorized access.
Indicators of compromise
- Packages
- @kl-dolphin/jump
Remediation
- Remove the @kl-dolphin/jump package immediately from all systems
- Rotate all secrets, keys, and credentials from a different, uncompromised computer
- Perform a full security audit and malware scan of any system that had the package installed
- Review system logs and access logs for signs of unauthorized activity or data exfiltration
- Consider the affected system(s) as potentially fully compromised and take appropriate incident response measures
- Verify the integrity of other installed packages and dependencies
Sources
- GitHub Advisory GHSA-wfwr-cf4w-fpj5 · GitHub Advisory Database
Cite this entry
"Malware in @kl-dolphin/jump." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 24, 2026; last updated June 24, 2026. https://supplychainattack.org/incident/malware-in-kl-dolphin-jump-1gx19d
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