Malicious Code Injection in rude_wren-notthedev Package: A Threat to npm Users

rude_wren-notthedev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108243: Malicious code in rude_wren-notthedev (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The rude_wren-notthedev package is part of the npm ecosystem, often utilized for various JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant issues in the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the rude_wren-notthedev package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, thereby polluting the npm registry. This behavior can lead to security risks, including the potential for developers to unknowingly use compromised packages in their applications.

How To Fix

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

npm uninstall rude_wren-notthedev

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 remove the affected package from your project by running: npm uninstall rude_wren-notthedev. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The rude_wren-notthedev package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications. Regular updates and monitoring tools like Vulert can aid in maintaining the integrity of your software.

See every vulnerability recorded for rude_wren-notthedev →

Share this vulnerability

FAQ

The rude_wren-notthedev package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

If your application uses the affected package, it may inadvertently include malicious code that can compromise the security and integrity of your software.

You should uninstall the package immediately and monitor for any updates or patches that may be released.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities using just your package-lock.json file. You can check your application using the Vulert playground at Vulert Scanner.

Regularly updating your dependencies, using tools like Vulert for monitoring, and conducting security audits can help prevent vulnerabilities in your applications.

How To Fix

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

npm uninstall rude_wren-notthedev

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