Malware in svelte-mapping-core
Malware was discovered in the npm package svelte-mapping-core. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- svelte-mapping-core
The npm package svelte-mapping-core was found to contain malware. According to the GitHub Advisory (GHSA-qq27-fv34-9cm7), 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. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a critical supply chain compromise affecting all users of the svelte-mapping-core package.
Indicators of compromise
- Packages
- svelte-mapping-core
Remediation
- Immediately isolate any computer with svelte-mapping-core installed from the network
- Rotate all secrets, API keys, credentials, and signing keys from a different, uncompromised computer
- Remove the svelte-mapping-core package from all affected systems
- Perform a full security audit and malware scan of affected systems
- Review all access logs and activity on affected systems for signs of unauthorized access
- Consider full system reimaging if the compromise is suspected to be deep or persistent
Sources
- GitHub Advisory GHSA-qq27-fv34-9cm7 · GitHub Advisory Database
Cite this entry
"Malware in svelte-mapping-core." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 6, 2026. https://supplychainattack.org/incident/malware-in-svelte-mapping-core-1r0p6c
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 santana-baileys (npm)
Malicious code discovered in santana-baileys npm package that covertly relays WhatsApp messaging data to an attacker-controlled endpoint (https://fiora.nixel.my.id/) via obfuscated character-code reconstruction in the message-send code path.
npmCompromised package - resolvedcritical
Malicious code in elephant-tusk-runner (npm)
The npm package elephant-tusk-runner contained malicious code that exposed a remote shell and remote code execution surface via an unauthenticated Express + WebSocket server binding to 0.0.0.0:4201 with fully open CORS. Any peer able to reach the port could execute arbitrary commands on the host.
npmCompromised package - resolvedcritical
Malicious code in @cats-cdf/browser-metrics-meter (npm)
The npm package @cats-cdf/browser-metrics-meter contained malicious code in its preinstall lifecycle script that exfiltrated system reconnaissance data (username, hostname, public IP) to an OAST collector domain. The package executed this behavior unconditionally on installation without consent or documented purpose.
npmCompromised package - resolvedcritical
Malicious code in @ks-video/kwai-player-web (npm)
The npm package @ks-video/kwai-player-web contained malicious code in its postinstall hook that exfiltrated system reconnaissance data (hostname, username, working directory, network interfaces, environment variable names) over plain HTTP to an unrelated third-party domain. The package has no legitimate relationship to the declared publisher Kwai/@ks-video.
npmCompromised package