Malicious Code Injection in grim_weasel_dumbs: A Threat to npm Users

grim_weasel_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103389: Malicious code in grim_weasel_dumbs (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

grim_weasel_dumbs is an npm package that is part of a broader campaign aimed at manipulating the npm registry for token rewards. This package, like others in the campaign, is designed to automatically generate and publish derivative packages with randomized names, which can inflate developer reputation scores. The malicious nature of this package poses a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in grim_weasel_dumbs arises from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, contributing to the pollution of the npm registry. This behavior is part of a larger scheme to exploit the npm ecosystem, potentially leading to the distribution of compromised packages and undermining trust in the registry.

How To Fix

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

npm uninstall grim_weasel_dumbs

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 grim_weasel_dumbs and any packages that depend on it. Regularly audit your dependencies using tools like npm audit or Vulert to identify and mitigate vulnerabilities. You can also use Vulert's playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without needing to sign up.

Conclusion

The grim_weasel_dumbs package poses a significant threat due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their projects remain secure.

See every vulnerability recorded for grim_weasel_dumbs →

Share this vulnerability

FAQ

grim_weasel_dumbs is an npm package involved in a malicious campaign to manipulate the npm registry for token rewards.

The vulnerability can lead to the injection of malicious code into your project, compromising its integrity and security.

You should uninstall the package immediately and check your project for any other affected packages.

You can use tools like npm audit or Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use Vulert's playground at Vulert Scanner to check for vulnerabilities in your application without needing to create an account.

How To Fix

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

npm uninstall grim_weasel_dumbs

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