Malicious Code Injection in sari-kepok71-wekto Package
Summary
MAL-2025-90356: Malicious code in sari-kepok71-wekto (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-kepok71-wekto package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. The primary functionality of this package is to serve as a component in the broader token reward system, but it has been compromised to include malicious code that affects its integrity and security.
Vulnerability Detail
The vulnerability in the sari-kepok71-wekto package originates from its inclusion in a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the security of the affected package but also pollutes the npm registry, potentially affecting other developers and their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sari-kepok71-wektoIf 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-kepok71-wekto package by using npm's package-lock.json file to lock the versions of your dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which allows you to check for open-source vulnerabilities in real-time without requiring code access or installation.
Conclusion
The sari-kepok71-wekto package has been identified as containing malicious code that compromises its integrity and the security of projects that depend on it. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for sari-kepok71-wekto →
FAQ
The sari-kepok71-wekto package is an npm package that is part of a token reward campaign, but it has been compromised to include malicious code.
The vulnerability can lead to the modification of your package.json file, removal of private flags, and pollution of the npm registry, which can impact other developers.
You should update the package to a patched version if available or remove it from your project to mitigate the risk.
You can use Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
