Malicious Code Detected in @bb1ptest23/test-paket: npm Package Vulnerability

@bb1ptest23/test-paket Updated 28 Sep 2026

Summary

28/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17201: Malicious code in @bb1ptest23/test-paket (npm). Affects @bb1ptest23/test-paket versions 1.0.3. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package @bb1ptest23/test-paket is an npm package designed for use in JavaScript applications. It is intended to facilitate specific functionalities within the npm ecosystem. However, this package has been flagged for containing malicious code, which poses significant risks to users and their applications.

Vulnerability Detail

The vulnerability in @bb1ptest23/test-paket arises from its communication with a domain associated with malicious activity. This behavior can lead to unauthorized data access, potential data breaches, and compromise of the user's system. Such vulnerabilities are particularly concerning as they can be exploited by attackers to execute harmful actions within the affected environment.

How To Fix

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

npm uninstall @bb1ptest23/test-paket

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 monitor your application for vulnerabilities using Vulert. By utilizing Vulert's playground at https://vulert.com/scanner, you can check if your application is affected by this vulnerability without requiring any signup. This tool analyzes your package-lock.json file to provide real-time alerts for open-source vulnerabilities.

Conclusion

The @bb1ptest23/test-paket npm package has been identified as malicious due to its communication with harmful domains. Users are advised to uninstall the package and consider alternatives. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for @bb1ptest23/test-paket →

Share this vulnerability

FAQ

The package communicates with a domain known for malicious activities, which can lead to security breaches.

You can check your package.json or package-lock.json files for the presence of @bb1ptest23/test-paket.

You should uninstall the package immediately using the command: npm uninstall @bb1ptest23/test-paket.

Yes, consider researching other npm packages that offer similar functionalities without the associated risks.

Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall @bb1ptest23/test-paket

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