Developers using the npm registry are being warned about dangerous fake packages that could lead to serious security risks. These malicious versions of tools like pgserve and automagik have been intentionally uploaded, aiming to infect computers and steal sensitive data. Installing these compromised packages could expose user tokens, passwords, cloud credentials, and even crypto assets stored in browsers. The threat also extends beyond the initial machine, as malware can spread to other connected devices.

Fake Packages Target Developers Looking for Popular Tools

Security researchers from two firms uncovered these malicious packages, which are designed to mimic legitimate ones. One set targets developers searching for pgserve, an embedded PostgreSQL server used for testing and development. The other fake packages impersonate automagik, an AI-powered coding tool. These fake versions have gained thousands of weekly downloads, making them easy to unknowingly install.

For example, the fake automagik/genie package had over 6,700 downloads per week, while the fake pgserve had about 1,300. The fake automagik versions ranged from 4.260421.33 to 4.260421.39. Researchers noted that more malicious versions are still being published, and the full extent of the compromise is still under investigation. The fake packages appear to be part of a larger campaign that resembles a recent supply chain attack called CanisterWorm, which replaced legitimate npm packages with malware.

Malware Capable of Data Theft and Self-Propagation

Researchers from StepSecurity identified specific malicious versions of pgserve, which inject a lengthy credential-harvesting script during installation. These infected packages, specifically versions 1.1.11, 1.1.12, and 1.1.13, run malicious code every time they are installed. The last safe version of pgserve was 1.1.10, and any newer versions should be considered compromised.

This malware is more than simple data theft. It’s a supply chain worm that can spread itself further if it finds an npm publish token on the infected machine. The malware re-injects itself into any package that token can publish, allowing it to spread rapidly across the npm ecosystem. The stolen data is encrypted and sent to a decentralized blockchain-based server, making it difficult for authorities to shut down or trace the attack.

Overall, this incident highlights how supply chain attacks are evolving. Threat actors are increasingly targeting open source software to infect a wide user base. Recent examples include hackers compromising the lead maintainer of popular libraries like Axios and several JavaScript testing utilities. These incidents serve as a warning for developers to be extra cautious when installing new packages.

Developers who have downloaded these malicious packages should act quickly to limit damage. Removing the fake packages, updating to clean versions, and changing any compromised credentials are crucial steps. It’s also recommended to audit npm tokens and monitor network activity for signs of malware spreading. Staying vigilant and verifying sources before installing new tools can help prevent falling victim to such sophisticated supply chain attacks.

Inspired by

• https://www.infoworld.com/article/4162198/malicious-pgserve-automagik-developer-tools-found-in-npm-registry.html

Sources

• socket.dev
• socket.dev
• stepsecurity.io
• csoonline.com
• csoonline.com