Malware - Fake npm Install Messages Spread RAT in Campaign
Basically, fake installation messages trick developers into installing malware on their computers.
A new malware campaign is deceiving developers through fake npm install messages. This clever tactic hides a RAT that steals sensitive data. Developers must be vigilant to protect their systems from this threat.
What Happened
A new and sophisticated software supply chain campaign is targeting developers via the npm package registry. Dubbed the Ghost campaign, it began in early February 2026. The campaign employs a set of deceptive npm packages designed to mislead developers into surrendering their system credentials while secretly deploying a remote access trojan (RAT) on their machines.
When a developer installs one of these malicious packages, it generates what appears to be a normal npm installation. The package displays log messages, shows a progress bar, and inserts random delays to create a realistic experience. However, none of the packages it claims to download actually exist, making it difficult for even experienced developers to detect the malicious activity.
Who's Being Targeted
The campaign primarily targets developers who frequently use the npm package registry. The seven identified packages include names like react-performance-suite, react-state-optimizer-core, and coinbase-desktop-sdk, all published by a user named “mikilanjillo.” This deceptive tactic is particularly concerning as it represents a shift in how threat actors operate within open-source ecosystems, making it harder to spot malicious intent.
In March 2026, further analysis revealed a related cluster, dubbed GhostClaw, which shares similar techniques and infrastructure. This indicates that the campaign may be broader than initially thought, potentially affecting a larger number of developers and projects.
Signs of Infection
One of the most deceptive elements of this campaign is how it tricks developers into providing their sudo password. The installation process generates an error about missing write permissions, prompting the developer to enter their root password. This request feels entirely expected, as permission errors during npm installs are common.
Once the password is entered, the malware's downloader runs silently while the fake logs continue to scroll, masking the malicious activity. The downloader then contacts a Telegram channel to fetch the final payload URL and its decryption key. This allows the RAT to be executed, granting attackers persistent access to the compromised system.
How to Protect Yourself
Developers should exercise caution when installing npm packages. Here are some key protective measures:
- Never enter your sudo or root password when prompted by an npm package during installation.
- Verify the package authors and repository history before installation.
- Utilize automated security scanning tools to identify suspicious scripts.
- Enforce strict dependency review workflows within organizations.
By treating any password prompts during software installations as major warning signs, developers can significantly reduce their risk of falling victim to such sophisticated attacks.
Cyber Security News