twork-data-services-procedure-engine-api-v1-procedure-infonpm
twork-data-services-procedure-engine-api-v1-procedure-info is a confirmed malicious npm package (MAL-2026-12295) that typosquats a legitimate package to trick installs (malicious version 20.6.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-procedure-engine-api-v1-procedure-info (npm)
What this malware does
On require of the package's main index.js, support.js reconstructs attacker-controlled hostnames from string-split arrays (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT fallback under dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site), downloads a platform-specific binary over HTTPS, writes it to /var/tmp/.cache<hex> on Unix or %TEMP%/dotnet_diag_<hex>.exe on Windows, chmods 0755, and spawns it detached via /bin/sh -c or cmd. No hash or signature verification is performed. Filenames and lock paths (analytics_state, dotnet_diag_*.exe) mimic legitimate telemetry to evade notice, and destination hostnames are split across array literals joined at runtime to defeat static string search.
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-procedure-engine-api-v1-procedure-info (version 20.6.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twork-data-services-procedure-engine-api-v1-procedure-info across your stack and pipelines.
If you installed it — respond
twork-data-services-procedure-engine-api-v1-procedure-info is a typosquat — you almost certainly intended a legitimately-named package. Remove twork-data-services-procedure-engine-api-v1-procedure-info, 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-procedure-engine-api-v1-procedure-info 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-procedure-engine-api-v1-procedure-info 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-procedure-engine-api-v1-procedure-info-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.