Malicious Code Injection in brandly-teadev Package

brandly-teadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100080: Malicious code in brandly-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 brandly-teadev package is part of the npm ecosystem, often utilized for various development tasks. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This package is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the brandly-teadev package being involved in a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes these variants, which can lead to reputation damage for developers and potential security risks for users who inadvertently install these malicious packages.

How To Fix

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

npm uninstall brandly-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 avoid using the brandly-teadev package until a secure version is released. Additionally, you can use the following command to uninstall the package: 'npm uninstall brandly-teadev'.

Conclusion

The brandly-teadev package has been identified as a malicious entity within the npm ecosystem, capable of compromising project security. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for brandly-teadev →

Share this vulnerability

FAQ

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

This vulnerability can lead to the installation of malicious packages that may compromise your project's security and integrity.

If you have installed the brandly-teadev package, it is crucial to uninstall it immediately and monitor your project for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

To prevent similar vulnerabilities, regularly update your dependencies, use trusted packages, and monitor your projects for vulnerabilities using tools like Vulert.

How To Fix

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

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