1-minute read
What a defender needs to know
Socket found 18 npm packages that combined into a cross-platform RAT targeting developers using Alibaba private tooling. The campaign split downloader behavior across ordinary-looking modules, then used an attacker-controlled rule to escape a Node.js vm sandbox and load later stages.
The final payload supported shell commands, file transfer, reverse proxying, platform-specific persistence, AI-tool injection, and DingTalk lateral movement. Socket did not identify the operator or confirm a victim count.
Search direct and transitive dependency history for all 18 names. On endpoints, hunt # __INJECT_MARKER__, ROBOT_UID=3201d407b7899a12d6d439950511c6a5, shell and Launch Agent changes, Alilang app.asar replacement, short-lived /tmp binaries, published hashes, and the listed network infrastructure.
Preserve evidence, isolate affected systems, and rotate npm, source-control, cloud, CI/CD, SSH, container, cluster, Vault, and collaboration credentials from a clean machine. Review use histories after the earliest possible install. Investigate dependency provenance, endpoint state, account activity, and DingTalk actions. Explicitly document missing telemetry and rebuild the system when it prevents a reliable assessment.
Review package-registry publication history for attacker-created releases and tokens.