twork-data-services-eacq-company-service-v2-api-v1-identifiers-crmnpm
twork-data-services-eacq-company-service-v2-api-v1-identifiers-crm is a confirmed malicious npm package (MAL-2026-12291) that steals credentials and exfiltrates sensitive data (malicious version 20.6.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twork-data-services-eacq-company-service-v2-api-v1-identifiers-crm (npm)
What this malware does
index.js unconditionally requires setup.js on module load. setup.js reconstructs C2 hostnames at runtime from split string fragments (resolving to oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, with a DNS-TXT fallback channel under *.dl.well1.site), downloads a platform-specific binary, writes it to a temp path with a masquerading filename (.cache_<hex>, dotnet_diag_<hex>.exe), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe with no hash or signature verification. The package's advertised purpose does not require any native binary. Environment variables such as DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, and DO_NOT_TRACK are checked to skip execution, consistent with sandbox/analyst evasion. A sibling module lib/telemetry.js, not currently reached from the entrypoint, ships the same spawn(/bin/sh) + chmodSync 0755 + base64-buffer decode pattern with split 'child_'+'process' require, indicating a staged alternate dropper bundled with the package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for twork-data-services-eacq-company-service-v2-api-v1-identifiers-crm (version 20.6.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twork-data-services-eacq-company-service-v2-api-v1-identifiers-crm across your stack and pipelines.
If you installed it — respond
twork-data-services-eacq-company-service-v2-api-v1-identifiers-crm is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If twork-data-services-eacq-company-service-v2-api-v1-identifiers-crm 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-eacq-company-service-v2-api-v1-identifiers-crm 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-eacq-company-service-v2-api-v1-identifiers-crm-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.