Critical Malicious Code Vulnerability in adminauthserv Package

adminauthserv Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14098: Malicious code in adminauthserv (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 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 adminauthserv package is a Node.js library designed to facilitate user authentication services in web applications. It is commonly used by developers to streamline the process of managing user sessions and permissions. However, this package has been identified to contain malicious code that poses significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability in the adminauthserv package arises from the inclusion of malicious code that can compromise the security of applications. This code may allow unauthorized access to sensitive data, lead to data breaches, or enable remote code execution. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall adminauthserv

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 measure, users can replace the adminauthserv package with alternative authentication libraries that do not have known vulnerabilities. Ensure to review the documentation for these alternatives to integrate them effectively into your application.

Conclusion

The adminauthserv package contains a critical vulnerability due to malicious code that can severely impact application security. Users are urged to remove the package and seek alternatives to safeguard their applications. Regular monitoring for vulnerabilities using tools like Vulert can help maintain security in open-source projects.

See every vulnerability recorded for adminauthserv →

Share this vulnerability

FAQ

adminauthserv is a Node.js library used for managing user authentication in web applications.

The malicious code can lead to unauthorized access, data breaches, or remote code execution.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Currently, there is no patched version available for the adminauthserv package. It is advised to remove the package and look for alternatives.

Remove the adminauthserv package from your project immediately and consider using alternative authentication libraries.

How To Fix

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

npm uninstall adminauthserv

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