Malicious Code Injection in nurul-serabi63-ruro: npm Package Vulnerability

nurul-serabi63-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106450: Malicious code in nurul-serabi63-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'nurul-serabi63-ruro' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate automated publishing of derivative packages, which can inflate developer reputation scores. This package has been identified as containing malicious scripts that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious scripts, which modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers by inflating reputation scores fraudulently. The malicious payload can also expose developers to security risks by allowing unauthorized access to their projects.

How To Fix

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

npm uninstall nurul-serabi63-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 package from executing by removing it from your project dependencies and ensuring that your package-lock.json file does not reference it. You can also use npm audit to check for vulnerabilities in your project.

Conclusion

The nurul-serabi63-ruro package poses a significant security risk due to its malicious code that alters project files and republishing behavior. It is crucial to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert to ensure the integrity of your software.

See every vulnerability recorded for nurul-serabi63-ruro →

Share this vulnerability

FAQ

The nurul-serabi63-ruro package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your project to security risks and affecting your reputation in the npm ecosystem.

You should uninstall the package immediately using 'npm uninstall nurul-serabi63-ruro' and check for any dependencies that may be affected.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly audit your dependencies using 'npm audit', keep your packages updated, and consider using tools like Vulert to monitor for vulnerabilities.

How To Fix

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

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