Malicious Code Injection in ideological_wolverine-notthedev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103941: Malicious code in ideological_wolverine-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 ideological_wolverine-notthedev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the ideological_wolverine-notthedev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, often themed around Indonesian culture. The malicious scripts (auto.js, autopublish.js, etc.) continuously republish these variants, leading to pollution of the npm registry and potential exploitation of developers who unknowingly use these packages. The ramifications include compromised developer reputations and the risk of introducing vulnerabilities into projects that depend on these packages.

How To Fix

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

npm uninstall ideological_wolverine-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, avoid using the ideological_wolverine-notthedev package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like Vulert to monitor for vulnerabilities.

Conclusion

The ideological_wolverine-notthedev package poses a significant security risk due to its malicious code that alters project files and pollutes the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert to ensure the security of their applications.

See every vulnerability recorded for ideological_wolverine-notthedev →

Share this vulnerability

FAQ

It is an npm package linked to the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file and can lead to the publication of compromised packages, affecting your project's integrity.

You should uninstall the package immediately using 'npm uninstall ideological_wolverine-notthedev' and check for any other affected packages.

You can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall ideological_wolverine-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