Malicious Code Injection in laila-lapis36-ruro Package

laila-lapis36-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104988: Malicious code in laila-lapis36-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 laila-lapis36-ruro package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate the development process by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing system, leading to significant security risks for developers and their applications.

Vulnerability Detail

The vulnerability in the laila-lapis36-ruro package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file, removing private flags and altering version numbers. This behavior not only compromises the integrity of the package but also leads to the proliferation of potentially harmful variants that can pollute the npm registry and inflate developer reputation scores fraudulently. The malicious payload can result in unauthorized access to sensitive data and can compromise the security of applications relying on this package.

How To Fix

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

npm uninstall laila-lapis36-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 laila-lapis36-ruro package and look for alternative packages that provide similar functionality without the associated risks. Always validate the source and integrity of packages before including them in your project.

Conclusion

The laila-lapis36-ruro package poses a significant security risk due to its malicious code injection. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for laila-lapis36-ruro →

Share this vulnerability

FAQ

The laila-lapis36-ruro package is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's security and integrity.

You should uninstall the laila-lapis36-ruro package immediately and look for secure alternatives.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

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 laila-lapis36-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