Malicious Code Injection in nurul-lumpur52-ruro Package

nurul-lumpur52-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106436: Malicious code in nurul-lumpur52-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 nurul-lumpur52-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 exploit the npm registry by generating numerous derivative packages with random names. The primary function of the package is to participate in the tea.xyz token reward campaign, which has led to the proliferation of malicious scripts designed to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the nurul-lumpur52-ruro package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and creates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious scripts included in this package are designed to automate the generation and publication of these variants, making it a significant threat to developers relying on the npm ecosystem.

How To Fix

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

npm uninstall nurul-lumpur52-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 temporarily avoid using the nurul-lumpur52-ruro package in your project. Additionally, consider using a tool like Vulert to monitor your package-lock.json file for any vulnerabilities in real-time. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without requiring any signup.

Conclusion

The nurul-lumpur52-ruro package poses a significant threat due to its malicious behavior aimed at exploiting the npm registry. It is crucial for developers to be aware of this vulnerability and take appropriate actions to safeguard their applications. Regular monitoring and updates are essential to maintain security in the npm ecosystem.

See every vulnerability recorded for nurul-lumpur52-ruro →

Share this vulnerability

FAQ

The nurul-lumpur52-ruro package is an npm package that is part of a malicious campaign aimed at exploiting the npm registry.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and affecting your application's security.

You should remove the nurul-lumpur52-ruro package from your project and monitor for any updates or patches that may be released.

Yes, Vulert allows you to monitor your package-lock.json file for vulnerabilities in real-time without requiring access to the code or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall nurul-lumpur52-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