twork-data-services-counterfreenpm

index.js unconditionally requires./init on load. init.js selects a platform-specific binary path, fetches an opaque payload over HTTPS from attacker-controlled Cloudflare Workers hosts whose hostnames are assembled at runtime by joining short string fragments (e.g. 'oob-worker.cf102' + '-baf.work' + 'ers.' + 'dev' → oob-worker.cf102-baf.workers.dev; sibling hosts oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev). If HTTPS mirrors are unreachable, the loader falls back to a DNS-TXT covert channel: it resolves TXT on c.<domain> under *.dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site) to obtain a chunk count, resolves numbered subdomains to collect base64 chunks, and reassembles the payload. The bytes are written to /tmp or %TEMP% under deceptive names masquerading as system tooling (dotnet_diag<rnd>.exe on Windows,.cache<rnd> /.analytics_state on POSIX), chmod 0o755 is applied on POSIX, and the binary is spawned detached via cp.spawn('/bin/sh', ['-c', fp+' &'], {detached:true}).unref() or the Windows cmd equivalent. Fires on require() of the package, so any consumer that installs and loads twork-data-services-counterfree executes attacker-controlled code with the installer's privileges.

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.