Malicious Code Vulnerability in sanctum-re-raimu: Exploitation of npm Packages
Summary
MAL-2025-165752: Malicious code in sanctum-re-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
sanctum-re-raimu is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate token rewards through various functionalities. However, this package has been identified as malicious, containing scripts that manipulate its own metadata and publish derivative packages to inflate developer reputation scores.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. These packages include scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to reputation inflation for developers and pollution of the npm registry, potentially compromising the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sanctum-re-raimu
If 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 measure, you can avoid using the sanctum-re-raimu package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unexpected changes.
Conclusion
The sanctum-re-raimu package has been identified as malicious, posing risks to developers and the npm ecosystem. It is crucial to remove this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for sanctum-re-raimu →
FAQ
The malicious code includes scripts that modify package metadata and publish derivative packages to inflate developer reputation scores.
You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without signing up.
It is advisable to remove the sanctum-re-raimu package immediately and check for any other affected packages in your project.
While specific exploits have not been detailed, the manipulation of package metadata can lead to broader security issues within the npm ecosystem.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to npm packages.