twork-data-services-proxy-invest-symbols-listnpm
twork-data-services-proxy-invest-symbols-list is a confirmed malicious npm package (MAL-2026-12298) that executes malicious code on install (malicious version 20.4.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-proxy-invest-symbols-list (npm)
What this malware does
On require() of this package, index.js loads init.js which immediately downloads a platform-specific binary from hardcoded Cloudflare Workers endpoints (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT base64 fallback via *.dl.well1.site. The fetched bytes are written to a temp path under disguised names (e.g. dotnet_diag.exe,.cache_), chmod 0755, and detached-spawned via /bin/sh -c or cmd.exe start /b. Hostnames are assembled at runtime from split string arrays (e.g. ['oob-worker.cf100-416.w','orkers.','dev'].join('')) to defeat static hostname scanning. Destination is not the publisher's infrastructure, the fetched payload is opaque, and the package name has no legitimate reason to fetch and run a binary at import time. Platform gating, cooldown flag files, and telemetry-styled opt-out env-var names are consistent with a dropper attempting to blend in.
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-proxy-invest-symbols-list (version 20.4.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-proxy-invest-symbols-list across your stack and pipelines.
If you installed it — respond
Remove twork-data-services-proxy-invest-symbols-list 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-proxy-invest-symbols-list 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-proxy-invest-symbols-list 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-proxy-invest-symbols-list-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.