Malicious Code Injection in sari-mangut39-riris Package

sari-mangut39-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90379: Malicious code in sari-mangut39-riris (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The sari-mangut39-riris 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 aims to exploit the npm registry by generating and publishing derivative packages with randomized names. The primary function of this package is to facilitate token rewards for the tea.xyz protocol, but it has been compromised to manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the sari-mangut39-riris package originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for dependency confusion attacks, where legitimate packages may be overshadowed by these malicious variants.

How To Fix

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

npm uninstall sari-mangut39-riris

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-mangut39-riris package and any packages that depend on it. Additionally, consider using a tool like Vulert to monitor your package-lock.json file for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The sari-mangut39-riris package poses a significant security risk due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for sari-mangut39-riris →

Share this vulnerability

FAQ

The sari-mangut39-riris package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

This vulnerability can lead to dependency confusion and may expose your application to security risks by allowing malicious packages to overshadow legitimate ones.

You should uninstall the sari-mangut39-riris package immediately and check for any dependencies that may rely on it.

Yes, you can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time.

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

How To Fix

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

npm uninstall sari-mangut39-riris

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