Malicious code in lakk-analytics (npm)
lakk-analytics@9.9.11 on npm contained malicious code that exfiltrated installer identity (OS username, hostname, working directory) via DNS queries to an out-of-band canary domain during npm install, despite the package README falsely claiming no network requests.
- Disclosed
- Last updated
- Blast radius
- All npm users who installed lakk-analytics@9.9.11
- Ecosystems
- Attack vectors
- Affected entities
- lakk-analytics · 9.9.11
lakk-analytics version 9.9.11 published to npm contained malicious code that executed during the npm install lifecycle. The package ran node index.js from an install hook, which loaded ./lib/core and constructed a subdomain from the installer's OS username, hostname, and current working directory, combined with a timestamp and the static prefix asnbank.\n\nThe malicious code then issued a dns.resolve4() query against oob.sl4x0.xyz, leaking installer identity information via DNS to an attacker-controlled out-of-band canary domain. The destination host and API surface were obfuscated using hex code-point arrays reconstructed with String.fromCharCode in sibling modules lib/b02e30.js and lib/6ad264.js.\n\nThe package README explicitly claimed "No network requests," directly contradicting the observed install-time DNS beacon behavior. This incident was identified and credited to the OpenSSF malicious-packages repository.
Indicators of compromise
- Packages
- lakk-analytics
- Domains
- oob.sl4x0.xyz
Remediation
- Immediately uninstall lakk-analytics@9.9.11 and any other versions from the same publisher
- Audit npm install logs for any installations of lakk-analytics@9.9.11
- Review DNS query logs for any queries to oob.sl4x0.xyz or similar subdomains
- Assume any system that installed lakk-analytics@9.9.11 may have had identity information (username, hostname, working directory) exfiltrated
- Use npm audit to check for this package in dependency trees
- Consider rotating credentials and reviewing access logs on systems where this package was installed
Sources
- GitHub Advisory GHSA-p9jp-9h4v-vpgv · GitHub Advisory Database
Cite this entry
"Malicious code in lakk-analytics (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malicious-code-in-lakk-analytics-npm-14f1fl
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package