Malicious Code Detected in frontend-auth-client Package

frontend-auth-client Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20968: Malicious code in frontend-auth-client (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The frontend-auth-client package is an npm library designed to facilitate authentication processes in web applications. It provides developers with tools to manage user sessions and secure access to resources. However, this package has been compromised, containing malicious code that poses significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability in the frontend-auth-client package stems from the inclusion of malicious code that can potentially compromise user data and application integrity. This issue originated from the package's codebase, which was found to be tampered with, allowing unauthorized access and manipulation of sensitive information. The ramifications of this vulnerability could include data breaches, unauthorized access to user accounts, and exploitation of application functionalities.

How To Fix

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

npm uninstall frontend-auth-client

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 frontend-auth-client package from your project until a secure version is available. You can do this by executing: npm uninstall frontend-auth-client. Alternatively, you may explore other authentication libraries that do not have known vulnerabilities.

Conclusion

The frontend-auth-client package has been identified as containing malicious code, posing serious security risks to applications that utilize it. It is crucial to update the package to a secure version or consider alternative solutions to mitigate these risks effectively.

See every vulnerability recorded for frontend-auth-client →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and manipulation of user data, posing significant security threats.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If immediate updates are not possible, consider removing the package or using alternative libraries until a secure version is released.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file.

Failure to address this vulnerability could result in data breaches, unauthorized access to user accounts, and exploitation of your application.

How To Fix

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

npm uninstall frontend-auth-client

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