twork-products-taiga2-products-investmentnpm
twork-products-taiga2-products-investment is a confirmed malicious npm package (MAL-2026-12305) that opens a backdoor for remote access (malicious version 20.2.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-products-taiga2-products-investment (npm)
What this malware does
On require of the package, init.js (unconditionally loaded from index.js) fetches a platform-specific executable from one of three obfuscated Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, cf102-baf.workers.dev, cf103-070.workers.dev), with a base64-over-DNS-TXT fallback via tin.dl.well1.site. The C2 hostnames are runtime-assembled from split string arrays to evade static inspection. The fetched binary is written to a disguised temp path (dotnet_diag<rand>.exe on Windows or.cache_<rand> on POSIX), chmod 0755, and spawned detached via /bin/sh -c '<path> &' or cmd.exe /c start /b, with a /tmp lock file gating re-execution. A second, currently-unreferenced dropper is also bundled at lib/telemetry.js under an 'analytics SDK' cover story, using string-concat require('child_'+'process') and the same fetch-write-chmod-spawn shape with a base64-chunked embedded buffer.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for twork-products-taiga2-products-investment (version 20.2.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twork-products-taiga2-products-investment across your stack and pipelines.
If you installed it — respond
twork-products-taiga2-products-investment establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If twork-products-taiga2-products-investment 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-products-taiga2-products-investment 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-products-taiga2-products-investment-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.