twork-data-services-aggregator-sme-task-infonpm
twork-data-services-aggregator-sme-task-info is a confirmed malicious npm package (MAL-2026-12288) that executes malicious code on install (malicious version 20.3.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-aggregator-sme-task-info (npm)
What this malware does
On require of this package, index.js loads runtime.js which asynchronously fetches a platform-specific binary from string-concatenation-obfuscated hosts (oob-worker.cf100-cf103-*.workers.dev, with a DNS-TXT chunked base64 fallback via tin/tina/ldr/win.dl.well1.site), writes it to /tmp as.cache<rand> or to %TEMP% as dotnet_diag_<rand>.exe, chmods it 755, and spawns it detached via /bin/sh -c or cmd.exe /c start. Destination hostnames and DNS resolvers are assembled at runtime via.join() over split string fragments to evade static inspection. No hash or signature verification is performed on the fetched bytes. A second, functionally equivalent dropper is shipped in lib/telemetry.js (mislabeled 'Analytics SDK'): base64 chunk reassembly, split-string require("child_"+"process"), fs["chmod"+"Sync"](path, 0o755), and cp.spawn("/bin/sh", ["-c", filePath+" &"], {detached:true}). Package name masquerades as an enterprise data-services utility; behavior is a load-time remote-code-execution dropper.
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-aggregator-sme-task-info (version 20.3.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-aggregator-sme-task-info across your stack and pipelines.
If you installed it — respond
Remove twork-data-services-aggregator-sme-task-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-aggregator-sme-task-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-aggregator-sme-task-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-aggregator-sme-task-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.