Malicious Code Injection in sari-getuk19-ruro: A Threat to npm Ecosystem

sari-getuk19-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108355: Malicious code in sari-getuk19-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 package 'sari-getuk19-ruro' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks to developers who may unknowingly incorporate these malicious packages into their projects.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the 'sari-getuk19-ruro' package. This 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. The primary risk is the potential for developers to inadvertently use these compromised packages, which can lead to further exploitation or data breaches.

How To Fix

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

npm uninstall sari-getuk19-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 workaround, you can avoid using the 'sari-getuk19-ruro' package and any other packages that are part of the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The 'sari-getuk19-ruro' package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers must take proactive steps to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.

See every vulnerability recorded for sari-getuk19-ruro →

Share this vulnerability

FAQ

It is an npm package associated with a token reward campaign that has been identified as malicious due to its behavior of generating and publishing derivative packages.

You can use Vulert's playground to check if your application is affected by this vulnerability without requiring any signup.

Using compromised packages can lead to security breaches, data leaks, and unauthorized access to your application and its users.

It is advisable to check for package updates regularly, ideally on a weekly basis, to ensure that you are using the latest and most secure versions.

If you have already used the 'sari-getuk19-ruro' package, you should remove it immediately and monitor your application for any unusual behavior.

How To Fix

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

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