twork-data-services-customer-api-v2-customer-vip-statusnpm
twork-data-services-customer-api-v2-customer-vip-status is a confirmed malicious npm package (MAL-2026-12290) that executes malicious code on install (malicious version 20.9.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-customer-api-v2-customer-vip-status (npm)
What this malware does
On require of this package, index.js loads platform.js which selects a platform-specific payload (linux_x64/linux_arm64/darwin/win32), downloads an opaque binary over HTTPS from a pool of *.workers.dev hosts, writes it to /var/tmp/.cache<hex> or %TEMP%/dotnet_diag_<hex>.exe, chmods it 0755, and spawns it detached via /bin/sh or cmd with unref, so execution survives the parent process. Destination hostnames are not stored as plain literals — they are assembled at runtime from split fragments (e.g. ['oob-worker.cf101-a','df.worke','rs.d','ev'].join('')) to evade string scans. If HTTPS retrieval fails, the code falls back to DNS TXT lookups against numbered subdomains of dl.well1.site and reassembles a base64-encoded binary from the concatenated TXT records, bypassing HTTPS egress inspection. The disguised on-disk filenames (dotnet_diag_,.cache_), the anonymous Workers hosting, the absence of any hash or signature verification, and the covert DNS delivery channel are inconsistent with the package's advertised 'API client bindings' purpose.
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-customer-api-v2-customer-vip-status (version 20.9.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twork-data-services-customer-api-v2-customer-vip-status across your stack and pipelines.
If you installed it — respond
Remove twork-data-services-customer-api-v2-customer-vip-status 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-customer-api-v2-customer-vip-status 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-customer-api-v2-customer-vip-status 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-customer-api-v2-customer-vip-status-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.