Malicious Code Injection in sari-kue43-riris Package: A Threat to npm Users
Summary
MAL-2025-90362: Malicious code in sari-kue43-riris (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 sari-kue43-riris package is part of a broader campaign associated with the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate the npm ecosystem by automatically generating and publishing derivative packages. Its primary function is to inflate developer reputation scores for rewards, but it poses significant risks due to its malicious behavior.
Vulnerability Detail
The vulnerability in the sari-kue43-riris package stems from its inclusion in a malicious campaign that floods the npm registry with harmful packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry, making it difficult for developers to trust legitimate packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation of these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sari-kue43-riris
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 workaround, you can prevent the installation of the sari-kue43-riris package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The sari-kue43-riris package poses a significant threat to npm users due to its malicious code that alters package metadata and floods the registry with harmful variants. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your projects.
See every vulnerability recorded for sari-kue43-riris →
FAQ
The sari-kue43-riris package is part of a malicious campaign that aims to manipulate the npm ecosystem for token rewards.
The vulnerability can compromise your project's integrity by introducing malicious code and polluting the npm registry.
You should remove the sari-kue43-riris package from your project and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring a signup.