Malicious Code Injection in nurul-kue73-pore Package

nurul-kue73-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98189: Malicious code in nurul-kue73-pore (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 nurul-kue73-pore 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 automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign. The vulnerability arises from the package's ability to modify its own metadata and continuously republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in the nurul-kue73-pore package originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to significant ramifications, including the potential for developers to unknowingly install compromised packages, which can introduce security risks into their applications. The technical aspects of this vulnerability involve the use of autopublish scripts that automate the creation and publication of these malicious packages.

How To Fix

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

npm uninstall nurul-kue73-pore

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 installation of the nurul-kue73-pore package by using npm's package-lock.json file to lock your dependencies. This will ensure that only the specified versions of packages are installed, thereby avoiding the malicious package. You can also use the following command to audit your dependencies for vulnerabilities: npm audit.

Conclusion

The nurul-kue73-pore package poses a significant security risk due to its malicious code that modifies package metadata and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for nurul-kue73-pore →

Share this vulnerability

FAQ

The nurul-kue73-pore package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The malicious code can modify your package.json file, remove private flags, and republish variants, potentially leading to security risks in your application.

If you have installed the nurul-kue73-pore package, you should uninstall it immediately using the command npm uninstall nurul-kue73-pore.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.

Yes, 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-kue73-pore

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