Malicious Code Injection in marxist_aardwolf_requirement Package

marxist_aardwolf_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95402: Malicious code in marxist_aardwolf_requirement (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The marxist_aardwolf_requirement package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks for users who inadvertently install it.

Vulnerability Detail

The vulnerability originates from the package being involved in a token reward campaign that floods npm with malicious packages. It contains scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional exposure of sensitive information and potential exploitation of the affected systems.

How To Fix

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

npm uninstall marxist_aardwolf_requirement

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 avoid using the marxist_aardwolf_requirement package and monitor your package-lock.json file for any unauthorized changes. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The marxist_aardwolf_requirement package poses a significant security risk due to its malicious code designed to manipulate npm registry and developer reputation. Immediate action is required to remove the package and monitor for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your project.

See every vulnerability recorded for marxist_aardwolf_requirement →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the exposure of sensitive information and the pollution of the npm registry, potentially affecting the integrity of your project.

You should uninstall the package immediately using 'npm uninstall marxist_aardwolf_requirement' and monitor your project for any unauthorized changes.

Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

You can check the vulnerability details on the Vulert website or refer to the GitHub repository for malicious packages.

How To Fix

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

npm uninstall marxist_aardwolf_requirement

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