twork-data-services-aggregator-company-sme-main-timeline-loader-with-customersnpm
twork-data-services-aggregator-company-sme-main-timeline-loader-with-customers is a confirmed malicious npm package (MAL-2026-12287) that executes malicious code on install (malicious version 20.3.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-aggregator-company-sme-main-timeline-loader-with-customers (npm)
What this malware does
On require(), index.js loads _bridge.js which assembles obfuscated Cloudflare Workers hostnames from split string literals (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) and downloads a platform-specific opaque binary via https.get. If HTTPS fails, a DNS-TXT covert-channel fallback queries c.<domain> for a chunk count then <i>.<domain> TXT records under tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site, base64-decoding the concatenated chunks. The bytes are written to a hidden path in /tmp or %TEMP%, chmodded 0755, and executed detached via spawn("/bin/sh", ["-c", fp+" &"]) or spawn("cmd",...). Cover strings such as "analytics_state" and "dotnet_diag" mask the behavior. The hosts are unrelated to any declared publisher, the fetched content is opaque and unverified, and execution fires automatically when any consumer imports the package.
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-company-sme-main-timeline-loader-with-customers (version 20.3.8). 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-company-sme-main-timeline-loader-with-customers across your stack and pipelines.
If you installed it — respond
Remove twork-data-services-aggregator-company-sme-main-timeline-loader-with-customers 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-company-sme-main-timeline-loader-with-customers 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-company-sme-main-timeline-loader-with-customers 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-company-sme-main-timeline-loader-with-customers-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.