Malicious npm Packages Deliver Cross-Platform RAT to Alibaba Users

Overview of the Alibaba Developer Tool Attack

Security researchers have uncovered a sophisticated software supply chain campaign involving 18 malicious npm packages designed to target developers using tools associated with the Alibaba Group. According to Socket, the campaign deploys a complex cross-platform remote access trojan equipped with reconnaissance, file transfer, and persistence mechanisms. The operation relies on typosquatting and dependency confusion techniques, mimicking private packages under the @ali scope to trick developers into incorporating malicious code into their dependency trees.

Technical Details and Infection Mechanism

Unlike traditional single-package malware drops, this campaign utilizes a multi-layered dependency structure to obscure its true intent. Top-layer packages act as decoys, sharing names with legitimate internal packages used within the targeted ecosystem. For example, an unscoped package named lib-mtop mirrors a private Alibaba package, while other wrappers such as aone-kit, aone-kit-cli, and aone-sandbox declare scoped dependencies to trigger automated installation routines.

Once installed in a vulnerable environment, the dependency tree bridges through a middle-layer component named smart-config-manager. This component fetches rule engine configurations from an external GitHub repository. The rule engine then leverages the native JavaScript vm module to execute environment-specific payloads based on the victim’s operating system.

To evade detection, the final payload is retrieved from a domain masquerading as Alibaba infrastructure (aone-cli-next.oss-cn-beijing.aliyuncs[.]com). The resulting backdoor grants attackers extensive capabilities:

• Command Execution: Arbitrary command execution on compromised developer workstations.
• File Management: Full upload and download capabilities for data exfiltration.
• Lateral Movement: Tools designed to spread further within corporate networks.
• Persistence: Malicious code injection into common enterprise collaboration apps including DingTalk, Wukong, and Qoder.

Attribution remains tentative, but code analysis reveals Chinese language comments and GitHub commits timestamped in the UTC+08:00 timezone, suggesting a threat actor focused on Chinese-speaking developer environments for potential industrial espionage.

Actionable Mitigations and Defense

Defenders managing JavaScript and Node.js environments must take proactive steps to detect and remediate potential supply chain exposure. When investigating how to detect malicious npm dependencies, security teams should prioritize the following steps:

• Dependency Auditing: Scan all package-lock.json and package.json files across internal repositories for unauthorized unscoped packages that mirror private enterprise naming conventions.
• Credential Rotation: Any system that has installed the identified malicious packages should be treated as fully compromised. Rotate API keys, deployment tokens, and enterprise credentials from a completely clean workstation.
• Network Monitoring: Inspect outbound traffic for anomalies connecting to suspicious cloud storage buckets or external repositories executing script loaders via curl or dynamic vm execution.
• Strict Registry Controls: Implement private registry proxies and policy-as-code guardrails to prevent developers from accidentally pulling unscoped public packages that collide with internal namespace scopes.

Related: AsyncAPI npm packages infected with credential-stealing malware, Jscrambler NPM Packages Poisoned in Supply Chain Attack