Malicious Code Injection in mcclure-teadev Package: A Threat to npm Ecosystem

mcclure-teadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105723: Malicious code in mcclure-teadev (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The mcclure-teadev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate development by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and their applications.

Vulnerability Detail

The vulnerability in the mcclure-teadev package originates from its association with a token reward campaign that floods npm with malicious packages. These packages contain scripts designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious code modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to reputation inflation and security risks for developers using these packages.

How To Fix

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

npm uninstall mcclure-teadev

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 workaround, you can avoid using the mcclure-teadev package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The mcclure-teadev package poses a significant security risk due to its malicious code designed to exploit npm's publishing system. Developers should take immediate action to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for mcclure-teadev →

Share this vulnerability

FAQ

The mcclure-teadev package is an npm package used in JavaScript development, but it has been identified as malicious due to its involvement in a token reward scheme.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

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

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for 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 mcclure-teadev

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