Malicious Code Injection in labour_mockingbird_dumbs Package

labour_mockingbird_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104968: Malicious code in labour_mockingbird_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 labour_mockingbird_dumbs package is part of the npm ecosystem, often used in JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been known to flood npm with packages that inflate developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the labour_mockingbird_dumbs package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the proliferation of unwanted packages in the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages. The malicious payload is part of a broader strategy to exploit the npm registry for token rewards.

How To Fix

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

npm uninstall labour_mockingbird_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, consider using a package manager that allows you to lock down your dependencies and avoid using the labour_mockingbird_dumbs package until a fix is available. You can also monitor your package-lock.json file for any changes that may indicate the presence of this malicious package.

Conclusion

The labour_mockingbird_dumbs package contains malicious code that poses a significant risk to the npm ecosystem and developers. It is crucial to remove this package from your projects and monitor for any potential vulnerabilities using tools like Vulert. Staying informed and proactive can help mitigate the risks associated with such vulnerabilities.

See every vulnerability recorded for labour_mockingbird_dumbs →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The vulnerability can lead to the proliferation of unwanted packages, compromising the integrity of your project and potentially introducing security risks.

You should uninstall the labour_mockingbird_dumbs package immediately and check for any dependencies that may rely on it.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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