Malicious Code Injection in lisa-sroto33-ruro Package

lisa-sroto33-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105244: Malicious code in lisa-sroto33-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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The lisa-sroto33-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity.

Vulnerability Detail

The vulnerability in the lisa-sroto33-ruro package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers and projects relying on npm packages. The origin of this issue is linked to a campaign aimed at exploiting the npm ecosystem for token rewards, making it a significant concern for developers.

How To Fix

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

npm uninstall lisa-sroto33-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 remove the lisa-sroto33-ruro package from your project to prevent any malicious activity. This can be done using the command: npm uninstall lisa-sroto33-ruro. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The lisa-sroto33-ruro package contains a significant vulnerability due to its malicious code that alters package metadata and pollutes the npm registry. It is essential for developers to take immediate action by uninstalling the package and monitoring their projects for vulnerabilities.

See every vulnerability recorded for lisa-sroto33-ruro →

Share this vulnerability

FAQ

The lisa-sroto33-ruro package is an npm package involved in the tea.xyz token reward campaign, which has been found to contain malicious code.

The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, potentially affecting other projects.

If you have installed the lisa-sroto33-ruro package, you should uninstall it immediately and check for any updates or patches.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground.

To prevent future vulnerabilities, regularly update your packages, use tools like Vulert for monitoring, and review package dependencies before installation.

How To Fix

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

npm uninstall lisa-sroto33-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