twork-data-services-sme-operations-authorizationsnpm
twork-data-services-sme-operations-authorizations is a confirmed malicious npm package (MAL-2026-12302) that executes malicious code on install (malicious version 20.8.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-sme-operations-authorizations (npm)
What this malware does
On require of the package, index.js loads compat.js which fetches a platform-specific binary from hostnames assembled by array-join to hide them from static scanners (oob-worker.cf102-baf.workers.dev, cf100-416.workers.dev, cf103-070.workers.dev, cf99-9b3.workers.dev), with a DNS TXT base64 chunked fallback via *.dl.well1.site resolvers. The fetched bytes are written to /var/tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmodded to 0755, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start. No hash or signature verification is performed on the downloaded binary. A parallel dropper implementation in lib/telemetry.js uses the same pattern (child_process required via string concatenation, chmodSync accessed via computed property name, base64-decoded payload buffer, detached shell spawn). The package declares no legitimate purpose that would justify fetching and executing an unsigned remote binary at import time.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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-operations-authorizations (version 20.8.9). 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-operations-authorizations across your stack and pipelines.
If you installed it — respond
Remove twork-data-services-sme-operations-authorizations 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-operations-authorizations 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-operations-authorizations 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-operations-authorizations-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.