Malicious Code Injection in sari-klentik53-pore: A Threat to npm Packages
Summary
MAL-2025-98333: Malicious code in sari-klentik53-pore (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'sari-klentik53-pore' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores in exchange for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'sari-klentik53-pore' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to confusion among developers, potential security risks, and a degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sari-klentik53-poreIf 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 this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include 'sari-klentik53-pore' or any related packages. You can also use Vulert to monitor your project for vulnerabilities without needing to install any additional software.
Conclusion
The 'sari-klentik53-pore' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their applications. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.
See every vulnerability recorded for sari-klentik53-pore →
FAQ
The impact includes potential security risks, pollution of the npm registry, and confusion among developers due to the proliferation of malicious packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you have installed 'sari-klentik53-pore', you should uninstall it immediately using 'npm uninstall sari-klentik53-pore' and check your package-lock.json for any references.
Currently, there is no specific patch for 'sari-klentik53-pore', but it is crucial to monitor for updates and remove the package.
Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential threats.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
