Malicious Code Injection in convinced_newt-toolteadev Package

convinced_newt-toolteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100976: Malicious code in convinced_newt-toolteadev (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 convinced_newt-toolteadev package is part of the npm ecosystem, primarily used for development tools and utilities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package is particularly vulnerable due to its association with scripts that manipulate package metadata and publish harmful variants.

Vulnerability Detail

The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which utilizes scripts (such as auto.js and autopublish.js) to modify the package.json file. These modifications include removing private flags, altering version numbers, and generating random package names, leading to the pollution of the npm registry. The malicious behavior can result in compromised developer accounts and a degraded reputation for legitimate packages.

How To Fix

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

npm uninstall convinced_newt-toolteadev

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 prevent the installation of the compromised package by using npm's package-lock.json file to lock dependencies. You can also monitor your project for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time without requiring code access. To check if your application is affected, visit the Vulert playground at https://vulert.com/scanner.

Conclusion

The convinced_newt-toolteadev package has been identified as vulnerable due to its involvement in a malicious campaign that modifies package metadata and publishes harmful variants. It is crucial to update or remove this package to protect your project from potential risks. Utilizing tools like Vulert can help monitor and alert you to such vulnerabilities in real-time.

See every vulnerability recorded for convinced_newt-toolteadev →

Share this vulnerability

FAQ

It is an npm package used for development tools, but it has been compromised to include malicious code.

The vulnerability can lead to the publication of malicious packages, potentially harming your project's reputation and security.

Yes, you can use Vulert to monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.

You should update the package to a patched version or remove it from your project to mitigate the risk.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

How To Fix

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

npm uninstall convinced_newt-toolteadev

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