Malicious Code Injection in lisa-getas75-ruro Package

lisa-getas75-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105215: Malicious code in lisa-getas75-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 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 lisa-getas75-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 aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in the lisa-getas75-ruro package originates from its association with the tea.xyz token reward campaign. It contains scripts designed to automatically generate and publish derivative packages with randomized names. This malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can lead to a compromised npm registry and potential security risks for developers relying on these packages.

How To Fix

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

npm uninstall lisa-getas75-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, you can avoid using the lisa-getas75-ruro package and replace it with a trusted alternative. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you in real-time for open-source 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 lisa-getas75-ruro package poses a significant risk due to its malicious code that alters package files and repopulates the npm registry with compromised versions. It is crucial for developers to remove this package and utilize monitoring tools like Vulert to safeguard their projects from similar vulnerabilities.

See every vulnerability recorded for lisa-getas75-ruro →

Share this vulnerability

FAQ

The lisa-getas75-ruro package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to the modification of your package.json file and the introduction of malicious code, which can compromise your project's integrity.

You should remove the lisa-getas75-ruro package from your project and monitor for any updates or patches.

You can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time using just your package-lock.json.

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 lisa-getas75-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