twork-data-services-sme-agent-company-relationnpm
twork-data-services-sme-agent-company-relation is a confirmed malicious npm package (MAL-2026-12301) that executes malicious code on install (malicious version 20.5.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-sme-agent-company-relation (npm)
What this malware does
index.js unconditionally requires./init on module load. init.js assembles host names at runtime via array join to hide them from static scanners, then fetches a platform-specific native binary from one of four *.workers.dev hosts (oob-worker.cf101-adf.workers.dev, cf99-9b3.workers.dev, cf103-070.workers.dev, cf100-416.workers.dev), with a DNS TXT base64 fallback channel enumerated over c.<resolver> and 0..N.<resolver> records under tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The fetched bytes are written to /tmp/.cache<rand> or %TEMP%/dotnet_diag<rand>.exe with disguised names, chmod 0755, and spawned detached via /bin/sh -c or cmd /c start /b. A second dropper implementation in lib/telemetry.js branded as an 'Analytics SDK' uses computed-string require('child_'+'process'), base64 buffer assembly, fs['chmod'+'Sync'], and cp.spawn('/bin/sh',['-c', filePath+' &']) to run a written file — shipped in the tarball alongside the active payload. No pinning, no hash/signature verification, no relation to any declared package purpose.
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-sme-agent-company-relation (version 20.5.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twork-data-services-sme-agent-company-relation across your stack and pipelines.
If you installed it — respond
Remove twork-data-services-sme-agent-company-relation 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-sme-agent-company-relation 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-sme-agent-company-relation 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-sme-agent-company-relation-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.