Malicious npm Packages Deploy Cross-Platform RAT Targeting Alibaba Developers

A cluster of malicious npm packages has been used to deliver a cross-platform remote access trojan against developers who use Alibaba-related tools.

The campaign hides its harmful code across several packages, making each part look ordinary when viewed on its own.

The attack relies on package names that imitate private Alibaba packages and adds malicious dependencies during installation.

This approach can expose developer workstations, source code, credentials, and internal collaboration environments to remote control.

Researchers at Socket.dev identified the activity after examining the lib-mtop package, which had received new versions after years of little activity.

Socket.dev said in a report shared with Cyber Security News (CSN) that the operation appears narrowly focused rather than widely distributed.

Although the malicious packages recorded limited downloads, the RAT’s ability to collect data, run commands, and move through DingTalk-related tools creates a potentially serious espionage risk for affected organizations.

Malicious npm Packages Deploy Cross-Platform RAT

The attackers used a layered dependency chain in which top-level lure packages copied the names of private packages under Alibaba’s ali scope.

When a developer installed one of these lookalikes, additional dependencies supplied the downloader and rule-processing components.

This technique reflects the wider risk seen in recent npm supply chain attacks, where a seemingly harmless dependency can become the entry point for a larger compromise.

The packages were published through different maintainer accounts, helping conceal their shared purpose.

The dependency chain fetched a configuration file from an attacker-controlled GitHub repository and saved it locally as .cloud-preferences.json.

A package named local-config-parser then evaluated the rules inside that file, allowing hidden code to run on the victim’s machine.

The malicious rule abused a known escape from Node.js virtual-machine isolation. It accessed the host process, recovered Node’s module-loading functions, and downloaded another payload from infrastructure hosted in Alibaba Cloud, likely to make malicious traffic appear less unusual.

The next stage profiles the host and selects a payload for macOS, Windows, or Linux.

On macOS, it adds persistence through .zshrc and a Launch Agent; on Windows, it replaces the app.asar file of the Alilang security application; on Linux, it runs a temporary binary in the background.

RAT Capabilities and Response

The final aone-cli payload is a remote access trojan built for systems connected to Alibaba’s internal development ecosystem.

It can execute shell commands, upload and download files, collect host details, stage additional payloads, and create an encrypted reverse TCP proxy.

Its focus on DingTalk, Wukong, and Qoder enterprise tools is particularly concerning.

The malware can alter Python scripts in application .skills directories so that a hidden script runs later, offering a route for persistence and lateral movement across developer environments.

This makes the campaign comparable to other developer-focused RAT malware campaigns, but its package impersonation and Alibaba-specific tooling suggest a more targeted objective.

The Chinese-language comments and China Standard Time commit metadata may point to a Chinese-speaking operator, though they do not establish attribution.

Teams that installed any listed package should treat the affected environment as compromised and begin remediation from a clean device.

They should preserve forensic evidence where possible, remove the packages, rotate exposed development and cloud secrets, and inspect Python files for the INJECTMARKER value.

Security teams should also identify every developer workstation that installed the affected dependencies, review suspicious DingTalk activity, and monitor for connections to the listed command-and-control infrastructure.

Reviewing requests that use forged DingTalk Origin and Referer headers can help uncover communications tied to this threat.

Organizations can reduce similar exposure by reviewing dependency changes before deployment and limiting package-install permissions in sensitive build environments.

Coverage of malicious package delivery methods and npm registry compromise incidents also underscores why developers must treat unexpected dependency updates as a security event.

Indicators of Compromise (IoCs):-

Note: IP addresses and domains are intentionally defanged (e.g., [.]) to prevent accidental resolution or hyperlinking. Re-fang only within controlled threat intelligence platforms such as MISP, VirusTotal, or your SIEM.