Critical Malicious Code Vulnerability in preview-server-auth-bounty Package

preview-server-auth-bounty Updated 02 Oct 2025

Summary

11/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6117: Malicious code in preview-server-auth-bounty (npm). Affects preview-server-auth-bounty versions >= 1.1.5. 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 preview-server-auth-bounty package is an npm module designed for server authentication functionalities. It is widely used in applications requiring secure user authentication processes. However, this package has been identified to communicate with a domain associated with malicious activities, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability arises from the package's communication with a malicious domain, which can lead to unauthorized access, data breaches, and exploitation of the affected applications. This issue was introduced in version 1.1.5 and can potentially compromise the integrity and confidentiality of user data.

How To Fix

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

npm uninstall preview-server-auth-bounty

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 preview-server-auth-bounty package from your project until a secure version is released. You can do this by executing: npm uninstall preview-server-auth-bounty.

Conclusion

The preview-server-auth-bounty package has a critical vulnerability due to its communication with a malicious domain. It is essential to update or remove the package to safeguard your application from potential security threats.

See every vulnerability recorded for preview-server-auth-bounty →

Share this vulnerability

FAQ

The vulnerability involves the package communicating with a domain linked to malicious activities, which can lead to security breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If immediate updates are not possible, consider removing the package from your project as a temporary measure.

Yes, it is advisable to check for a patched version of the preview-server-auth-bounty package and update to that version.

Failing to address this vulnerability can lead to unauthorized access, data breaches, and exploitation of your application, compromising user data and trust.

How To Fix

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

npm uninstall preview-server-auth-bounty

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