Malicious Code Injection in vera-lapis80-ruro Package

vera-lapis80-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110398: Malicious code in vera-lapis80-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 vera-lapis80-ruro package is part of the npm ecosystem, often utilized for various JavaScript projects. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate package metadata and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in the vera-lapis80-ruro package stems from its association with 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, polluting the npm registry. This behavior can lead to security risks, including the potential for unauthorized access to sensitive information and the compromise of project integrity.

How To Fix

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

npm uninstall vera-lapis80-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 measure, you can avoid using the vera-lapis80-ruro package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The vera-lapis80-ruro package poses significant security risks due to its malicious code injection. It is crucial to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert. Staying informed and proactive can help safeguard your applications from potential threats.

See every vulnerability recorded for vera-lapis80-ruro →

Share this vulnerability

FAQ

The vera-lapis80-ruro package is an npm package that has been identified as part of a malicious campaign to manipulate package metadata.

This vulnerability can compromise your project's integrity by introducing malicious code and potentially exposing sensitive information.

You should uninstall the vera-lapis80-ruro package immediately and monitor your project for any signs of compromise.

You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

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 vera-lapis80-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