Malicious Code Vulnerability in san-cookik-raimu: Exploitation of npm Registry
Summary
MAL-2025-165748: Malicious code in san-cookik-raimu (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The package 'san-cookik-raimu' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior compromises the integrity of the npm registry and poses risks to developers and users relying on these packages.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the 'san-cookik-raimu' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also undermines the trustworthiness of the packages available to developers, potentially leading to the installation of compromised software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall san-cookik-raimuIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, consider removing the 'san-cookik-raimu' package from your project until a secure version is released. You can do this by executing: 'npm uninstall san-cookik-raimu'. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'san-cookik-raimu' package contains malicious code that poses significant risks to developers and users. It is crucial to update or remove this package and utilize tools like Vulert to monitor for vulnerabilities in your software. Staying vigilant and proactive can help maintain the integrity of your applications.
See every vulnerability recorded for san-cookik-raimu →
FAQ
The main issue is the presence of malicious code that modifies package metadata and repopulates the npm registry with compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. Visit Vulert Scanner to check your application without any signup.
Using the compromised package can lead to the installation of malicious software, data breaches, and a loss of trust in the npm ecosystem.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid using unverified packages.
If you have already installed the vulnerable package, uninstall it immediately and check for any unauthorized changes in your project.
