Malicious Code Injection in marxist_alpaca_dumbs Package

marxist_alpaca_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105640: Malicious code in marxist_alpaca_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The marxist_alpaca_dumbs package is part of the npm ecosystem, typically used for various JavaScript applications. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. It employs scripts that automatically publish variants with randomized names, compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package being part of a broader malicious campaign associated with the tea.xyz token reward initiative. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting developers who rely on these packages for legitimate purposes.

How To Fix

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

npm uninstall marxist_alpaca_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 workaround, avoid using the marxist_alpaca_dumbs package and consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The marxist_alpaca_dumbs package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be aware of such vulnerabilities and take immediate action to remove affected packages and monitor their applications for security.

See every vulnerability recorded for marxist_alpaca_dumbs →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application if you inadvertently use affected packages.

You should uninstall the marxist_alpaca_dumbs package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

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