Malicious Code Injection in vida-lapis66-riris Package - npm Vulnerability

vida-lapis66-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91811: Malicious code in vida-lapis66-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 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 vida-lapis66-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 npm's publishing system. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards associated with the tea protocol.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that includes autopublish scripts. These scripts modify the package.json file to remove private flags, change version numbers, and generate random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to security risks for developers who unknowingly install these compromised packages. The malicious payload can compromise the integrity of the npm ecosystem and affect applications relying on these packages.

How To Fix

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

npm uninstall vida-lapis66-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, avoid using the vida-lapis66-riris package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The vida-lapis66-riris package poses a significant security risk due to its malicious code designed to exploit the npm ecosystem. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain application security.

See every vulnerability recorded for vida-lapis66-riris →

Share this vulnerability

FAQ

The vida-lapis66-riris package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

If your application uses the vida-lapis66-riris package, it may be at risk of security breaches due to the malicious code that modifies package configurations and republish variants.

You should uninstall the vida-lapis66-riris package immediately and check for any dependencies that may rely on it. Use npm uninstall vida-lapis66-riris to remove it.

Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground.

Regularly audit your dependencies using npm audit and consider using tools like Vulert to monitor for vulnerabilities in your open-source packages.

How To Fix

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

npm uninstall vida-lapis66-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