Critical Malicious Code Vulnerability in failing-code Package

failing-code Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20162: Malicious code in failing-code (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 failing-code package is an npm library designed for developers to implement specific functionalities in their applications. It is widely used due to its ease of integration and robust features. However, it has been identified to contain malicious code that poses significant security risks to applications utilizing this package.

Vulnerability Detail

The vulnerability in the failing-code package originates from the inclusion of malicious code that can compromise the security of applications. This code can lead to unauthorized access, data breaches, and potential exploitation of user data. The vulnerability affects all versions of the package starting from version 0, making it critical 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 failing-code

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 failing-code package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall failing-code'. This will prevent the malicious code from executing in your application.

Conclusion

The failing-code package has been identified to contain malicious code, posing a significant risk to applications that utilize it. Immediate action is required to update or remove the package to safeguard your application and user data. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for failing-code →

Share this vulnerability

FAQ

The failing-code package is an npm library used for various functionalities in applications, but it has been found to contain malicious code.

The malicious code can lead to unauthorized access and data breaches, compromising the security of your application and user data.

You should immediately update the package to a patched version or uninstall it until a secure version is available.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall failing-code

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