twork-data-services-proxy-b2b-crm-api-v1-partners-companies-infonpm
twork-data-services-proxy-b2b-crm-api-v1-partners-companies-info is a confirmed malicious npm package (MAL-2026-12297) that executes malicious code on install (malicious version 20.5.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-proxy-b2b-crm-api-v1-partners-companies-info (npm)
What this malware does
On require() of the package, index.js invokes setup() in helpers.js which downloads a platform-specific native binary from split-string-obfuscated Cloudflare Workers hostnames (oob-worker.cf100-416/cf103-070/cf101-adf/cf102-baf.workers.dev) with a base64-over-DNS-TXT fallback via *.dl.well1.site, writes it to /tmp or %TEMP% under a hidden/disguised name (.cache<hex> or dotnet_diag_<hex>.exe), chmods it 0755, and launches it detached via /bin/sh -c or cmd.exe /c start /b. Endpoint hostnames and sensitive API names (child_process, chmodSync) are assembled with.join("") over split fragments to evade static matching, and cover-story identifiers (analytics_state, telemetry, DISABLE_TELEMETRY) frame the behavior as opt-out telemetry. A parallel dropper implementation with the same download-write-chmod-spawn shape is bundled in lib/telemetry.js. The package advertises only 'API client bindings' and ships no legitimate reason to fetch and execute an opaque native binary.
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-b2b-crm-api-v1-partners-companies-info (version 20.5.1). 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-b2b-crm-api-v1-partners-companies-info across your stack and pipelines.
If you installed it — respond
Remove twork-data-services-proxy-b2b-crm-api-v1-partners-companies-info 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-b2b-crm-api-v1-partners-companies-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-proxy-b2b-crm-api-v1-partners-companies-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-proxy-b2b-crm-api-v1-partners-companies-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.