Malicious Code Injection in sari-lengko14-ruro Package

sari-lengko14-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108363: Malicious code in sari-lengko14-ruro (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The sari-lengko14-ruro package is part of the npm ecosystem, primarily used for various JavaScript applications. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages, aimed at inflating developer reputation scores for token rewards. The package's functionality is compromised due to the presence of malicious scripts that manipulate its metadata.

Vulnerability Detail

The vulnerability originates from the package being part of a broader malicious campaign associated with the tea.xyz token reward initiative. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall sari-lengko14-ruro

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, avoid using the sari-lengko14-ruro package and consider using alternative packages that provide similar functionality without the risk of malicious code.

Conclusion

The sari-lengko14-ruro package is compromised by malicious code that alters its metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their applications for any potential impacts. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for sari-lengko14-ruro →

Share this vulnerability

FAQ

sari-lengko14-ruro is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The malicious code modifies your package.json file and can lead to the installation of compromised packages, potentially exposing your application to security vulnerabilities.

You should uninstall the sari-lengko14-ruro package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check if your application is affected by visiting the Vulert playground.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall sari-lengko14-ruro

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback