lakk-analyticsnpm

[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.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.