twork-data-services-invest-box-accountnpm
twork-data-services-invest-box-account is a confirmed malicious npm package (MAL-2026-12293) that executes malicious code on install (malicious version 20.8.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-invest-box-account (npm)
What this malware does
On module load, index.js requires./adapter.js which detects OS/architecture, fetches an opaque binary via https.get from string-concatenated Cloudflare Workers hostnames (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) and, on failure, reconstructs the payload from base64-encoded DNS TXT records under well1.site subdomains (tin/tina/ldr/win.dl.well1.site). The fetched bytes are written to /tmp or %TEMP% under masquerading names such as dotnet_diag* and.cache_*, chmod 755'd on Unix, and spawned detached via spawn('/bin/sh', ['-c', path+' &']) or cmd.exe /c start /b on Windows. Hostnames are assembled via Array.join('') splits to defeat plain-string scanners. No hash or signature verification is performed, no publisher-matched host is used, and the delivered bytes are opaque. The package presents itself as a telemetry/analytics helper.
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-invest-box-account (version 20.8.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twork-data-services-invest-box-account across your stack and pipelines.
If you installed it — respond
Remove twork-data-services-invest-box-account 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-invest-box-account 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-invest-box-account 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-invest-box-account-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.