twork-data-services-role-appnpm
twork-data-services-role-app is a confirmed malicious npm package (MAL-2026-12300) that executes malicious code on install (malicious version 20.9.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-role-app (npm)
What this malware does
On require(), index.js loads init.js which downloads a platform-specific executable from hardcoded Cloudflare Workers hosts assembled via split-string obfuscation (oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev). The binary is written to /var/tmp or %TEMP% under disguised names (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmod 0755, and spawned detached via spawn("/bin/sh", ["-c", path + " &"], {detached:true}) or spawn("cmd",...). When HTTPS retrieval fails, the loader falls back to a DNS-TXT covert channel at c.<domain> / N.<domain> under *.dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site), concatenates base64-encoded TXT chunks, and executes the reconstructed bytes with no verification. Host strings and the child_process module name are reconstructed from split fragments (e.g. ["oob-work","er.cf102-baf.","workers.de","v"].join(""); require("child_" + "process")) to evade static analysis. Installing or requiring this package auto-executes attacker-controlled code on the installer's machine.
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-role-app (version 20.9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twork-data-services-role-app across your stack and pipelines.
If you installed it — respond
Remove twork-data-services-role-app 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-role-app 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-role-app 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-role-app-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.