Which versions of lakk-analytics are malicious?

The following npm versions of lakk-analytics are flagged malicious: 9.9.11. Treat any of these as compromised.

How do I remediate lakk-analytics if I installed it?

lakk-analytics establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed lakk-analytics — how do I know if it already compromised me?

If lakk-analytics was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is lakk-analytics part of a known attack campaign?

Yes — lakk-analytics is associated with the IN-MAL-2026-015794 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find lakk-analytics across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for lakk-analytics (version 9.9.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lakk-analytics across your stack and pipelines.

Malicious package

lakk-analyticsnpm

lakk-analytics is a confirmed malicious npm package (MAL-2026-13348) that opens a backdoor for remote access (malicious version 9.9.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lakk-analytics (npm)

MAL-2026-13348

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall lakk-analytics

What this malware does

[email protected] runs node index.js from an npm install lifecycle hook, which loads ./lib/core and constructs a subdomain from the installer's OS username, hostname, and current working directory (with a timestamp and the static prefix asnbank), then issues a dns.resolve4() query against <prefix>.<user>.<host>.<cwd>.<ts>.oob.sl4x0.xyz. This leaks installer identity via DNS to an out-of-band canary domain on every install. The destination host oob.sl4x0.xyz and API surface (os, dns, process, userInfo, hostname, cwd) are hidden as hex code-point arrays reconstructed with String.fromCharCode in sibling modules lib/b02e30.js and lib/6ad264.js. The README explicitly claims 'No network requests', which directly contradicts the observed install-time DNS beacon.

Malicious versions

1 flagged

9.9.11

Indicators of compromise (SHA-256)

d9a1a1a5f0fd81e6ba6198e7f4cbdeab1c16b8ceed3dbb7becc6b4b6f611ad52

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for lakk-analytics (version 9.9.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lakk-analytics across your stack and pipelines.
If you installed it — respond
lakk-analytics establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If lakk-analytics was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks lakk-analytics before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. lakk-analytics on npm has been identified as a malicious package (version 9.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015794

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks lakk-analytics-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database