twork-data-services-counterfreenpm
twork-data-services-counterfree is a confirmed malicious npm package (MAL-2026-12289) that executes malicious code on install (malicious version 20.1.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-counterfree (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for twork-data-services-counterfree (version 20.1.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twork-data-services-counterfree across your stack and pipelines.
If you installed it — respond
Remove twork-data-services-counterfree from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If twork-data-services-counterfree 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 twork-data-services-counterfree 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks twork-data-services-counterfree-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.