Malicious Code Detected in fast-long-secure-function-bundle: A Critical Security Alert

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20238: Malicious code in fast-long-secure-function-bundle (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 package 'fast-long-secure-function-bundle' is an npm package designed to provide secure and efficient long-function handling in JavaScript applications. It is commonly used by developers to enhance performance and security in their code. However, it has been identified to contain malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in 'fast-long-secure-function-bundle' arises from the presence of malicious code embedded within the package. This code can potentially lead to unauthorized access, data breaches, or other malicious activities within applications that rely on this package. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall fast-long-secure-function-bundle

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 using alternative packages that provide similar functionality without the associated risks. Always review the security status of any package before integrating it into your project.

Conclusion

The discovery of malicious code in the 'fast-long-secure-function-bundle' package highlights the importance of vigilance in managing open-source dependencies. Users must take immediate action to remove the affected package and consider alternatives to safeguard their applications.

See every vulnerability recorded for fast-long-secure-function-bundle →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications using this package.

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

Immediately remove the package from your project and consider using a secure alternative.

Currently, there is no patched version available for the 'fast-long-secure-function-bundle' package.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall fast-long-secure-function-bundle

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