Malicious Code Injection in sari-telurtahu32-ruro Package

sari-telurtahu32-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108386: Malicious code in sari-telurtahu32-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The sari-telurtahu32-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages to inflate developer reputation scores. The package's functionality is compromised due to its involvement in generating and publishing random packages with malicious intent.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that utilizes autopublish scripts to create and publish numerous derivative packages. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. The malicious behavior can result in developers unknowingly using compromised packages, which may introduce security risks into their applications.

How To Fix

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

npm uninstall sari-telurtahu32-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 workaround, avoid using the sari-telurtahu32-ruro package and any packages that may depend on it. Regularly audit your package-lock.json file for any malicious packages. You can also use tools like Vulert to monitor your project for vulnerabilities without needing to access the code directly.

Conclusion

The sari-telurtahu32-ruro package poses a significant security risk due to its malicious code injection. It is crucial for developers to remove this package from their projects and monitor for any potential vulnerabilities using tools like Vulert. Staying informed and proactive can help mitigate the risks associated with such vulnerabilities.

See every vulnerability recorded for sari-telurtahu32-ruro →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

If your application uses the sari-telurtahu32-ruro package, it may be at risk of incorporating malicious code that can compromise its security.

You should uninstall the sari-telurtahu32-ruro package immediately and check for any dependent packages that may also be affected.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall sari-telurtahu32-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