Malicious Code Injection in lisa-wajit33-wekto Package
Summary
MAL-2025-87977: Malicious code in lisa-wajit33-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 lisa-wajit33-wekto package is part of the npm ecosystem, often used for various JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to manipulate developer reputation scores for token rewards, posing significant risks to users and developers alike.
Vulnerability Detail
The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, ultimately polluting the npm registry. The ramifications include potential security risks for applications relying on this package and the degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lisa-wajit33-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 avoid using the lisa-wajit33-wekto package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The lisa-wajit33-wekto package poses significant security risks due to its involvement in a malicious campaign. It is crucial for developers to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the integrity and security of your software.
See every vulnerability recorded for lisa-wajit33-wekto →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to security risks, including the potential for malicious code execution and the pollution of the npm registry.
You should uninstall the package immediately and monitor for any updates or patches that may be released.
Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without requiring any signup.
Vulert monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json, helping you maintain the security of your applications.
