Malicious Code Injection in lina-semur77-ruro Package - npm Vulnerability

lina-semur77-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105179: Malicious code in lina-semur77-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 lina-semur77-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that automate the generation and publication of derivative packages, potentially harming developers and users alike.

Vulnerability Detail

The vulnerability in the lina-semur77-ruro package originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names and continuously republishes variants to pollute the npm registry. This can lead to a compromised development environment, where developers may unknowingly use these malicious packages, risking their projects and reputations.

How To Fix

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

npm uninstall lina-semur77-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 prevent the installation of this package by using npm's package-lock.json to monitor your dependencies. If you are using Vulert, you can check your application for vulnerabilities without any installation. Simply visit the Vulert playground at https://vulert.com/scanner and upload your package-lock.json file to see if your application is affected.

Conclusion

The lina-semur77-ruro package poses a significant risk due to its malicious code that alters project configurations and can lead to further vulnerabilities. It is crucial to remove this package and monitor your dependencies for any similar threats. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for lina-semur77-ruro →

Share this vulnerability

FAQ

The lina-semur77-ruro package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.

This vulnerability can compromise your project by introducing malicious code that alters your package.json file and potentially leads to the installation of harmful packages.

If you have installed the lina-semur77-ruro package, you should remove it immediately and check for any other affected packages in your project.

You can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in your software by analyzing your package-lock.json file.

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

How To Fix

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

npm uninstall lina-semur77-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