twork-data-services-getting-arrestsnpm
twork-data-services-getting-arrests is a confirmed malicious npm package (MAL-2026-12292) that typosquats a legitimate package to trick installs (malicious version 20.1.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-getting-arrests (npm)
What this malware does
[email protected] acts as a binary dropper. index.js top-level requires./support.js, whose start() runs at load time: it selects a platform-specific endpoint, downloads a payload from one of several Cloudflare Workers hosts whose hostnames are assembled at runtime by string fragment concatenation (e.g. ["oob-w","orker.cf","99-9b3",".workers.d","ev"].join("")) with a DNS TXT fallback under *.dl.well1.site, writes it to /tmp or %TEMP% under a disguised filename (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmods 0755, and detach-spawns it via /bin/sh -c '<file> &' or cmd.exe /c start. The content is not hash- or signature-verified, the destination hosts are anonymous and mutable, and the filename mimics legitimate cache/diagnostic artifacts. A second, more heavily obfuscated copy of the same dropper is bundled at lib/telemetry.js under cover-story class names (Logger, HttpTransport, ServiceDiscovery, WorkerHost) using the same primitives (Buffer.from(chunks,'base64'), cp.spawn('/bin/sh', ['-c', filePath + ' &']), fs['chmod'+'Sync'], require('child_'+'process')). Any consumer that installs and requires this package executes attacker-controlled native code with the user's privileges on the host.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for twork-data-services-getting-arrests (version 20.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twork-data-services-getting-arrests across your stack and pipelines.
If you installed it — respond
twork-data-services-getting-arrests is a typosquat — you almost certainly intended a legitimately-named package. Remove twork-data-services-getting-arrests, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If twork-data-services-getting-arrests 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-getting-arrests 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-getting-arrests-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.