twork-data-services-proxy-prime-api-v1-account-overdraft-infonpm
twork-data-services-proxy-prime-api-v1-account-overdraft-info is a confirmed malicious npm package (MAL-2026-12299) that executes malicious code on install (malicious version 20.7.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-proxy-prime-api-v1-account-overdraft-info (npm)
What this malware does
On require() of this package, index.js loads adapter.js which selects a platform-specific asset path (/pkg/package, /pkg/package.exe, /pkg/loader_mac, /pkg/package-arm64) and fetches an opaque native executable over HTTPS from hostnames reconstructed at runtime via array-join fragments (oob-worker.cf*-*.workers.dev), with a DNS TXT chunked-base64 fallback under *.dl.well1.site. The downloaded bytes are written to /var/tmp/.cache<rand> or %TEMP%/dotnet_diag_<rand>.exe, chmod'd 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Network destinations and sensitive API names (child_process, chmodSync) are assembled from split string fragments to evade static grepping. A second unreferenced dropper implementation in lib/telemetry.js (self-described 'Analytics SDK', 81KB) mirrors the same primitives at larger scale (cp.spawn('/bin/sh', ['-c', filePath+' &'], {detached:true}), fs['chmod'+'Sync'], base64 chunk decoding). The fetched payload host is unrelated to any stated package purpose, is mutable and anonymously-hosted, and delivers arbitrary native code that runs with the installer's privileges on every require.
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-prime-api-v1-account-overdraft-info (version 20.7.4). 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-prime-api-v1-account-overdraft-info across your stack and pipelines.
If you installed it — respond
Remove twork-data-services-proxy-prime-api-v1-account-overdraft-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-prime-api-v1-account-overdraft-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-prime-api-v1-account-overdraft-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-prime-api-v1-account-overdraft-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.