Malicious Code Injection in Turner-Teadev Package: A Threat to npm Ecosystem

turner-teadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109861: Malicious code in turner-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 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 'turner-teadev' package is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate development workflows by providing reusable code modules. However, this package has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, potentially compromising the integrity of projects that depend on it.

Vulnerability Detail

The vulnerability stems from the 'turner-teadev' package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may introduce security risks and instability into their applications.

How To Fix

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

npm uninstall turner-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 temporary workaround, you can remove the 'turner-teadev' package from your project by executing: 'npm uninstall turner-teadev'. This will prevent any potential malicious code from executing in your application.

Conclusion

The 'turner-teadev' package poses a significant risk due to its association with malicious activities in the npm ecosystem. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive steps, you can safeguard your applications from potential threats.

See every vulnerability recorded for turner-teadev →

Share this vulnerability

FAQ

The 'turner-teadev' package is a JavaScript package available on npm, intended for use in development workflows.

If your project depends on the 'turner-teadev' package, it may inadvertently use malicious code that can compromise your application's security and integrity.

You should uninstall the 'turner-teadev' package immediately and check for any other dependencies that may be affected.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.

Regularly update your dependencies, use tools like Vulert for monitoring vulnerabilities, and review package sources before installation.

How To Fix

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

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