Malicious Code Detected in bttr-devs Package - Critical Vulnerability Alert

bttr-devs Updated 23 Jan 2026

Summary

23/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-477: Malicious code in bttr-devs (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 bttr-devs package is a Node.js library commonly used in various applications for development purposes. It provides developers with tools and utilities to enhance their workflow. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability originates from the bttr-devs package, which has been identified to contain malicious code that can compromise the security of applications using it. This malicious code could lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The vulnerability affects all versions of the package starting from its introduction, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall bttr-devs

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 removing the bttr-devs package from your project until a secure version is released. You can do this by executing the following command: npm uninstall bttr-devs. Additionally, monitor your application for any suspicious activity during this period.

Conclusion

The discovery of malicious code in the bttr-devs package poses a serious threat to applications utilizing it. Immediate action is required to mitigate risks by updating or removing the package. Continuous monitoring and utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for bttr-devs →

Share this vulnerability

FAQ

bttr-devs is a Node.js library used by developers to enhance their development workflow with various tools and utilities.

The malicious code was detected through an automated security assessment conducted by Amazon Inspector, which identified the presence of harmful code within the package.

Using the compromised bttr-devs package can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time by analyzing your package-lock.json file. You can check your application's vulnerability status using the Vulert playground without any signup.

If you are affected, immediately uninstall the bttr-devs package and monitor your application for any unusual activity. Update to a secure version as soon as it becomes available.

How To Fix

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

npm uninstall bttr-devs

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