Malicious Code Detected in fireasp Package - Security Alert

fireasp Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20584: Malicious code in fireasp (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The fireasp package is a Node.js library designed to facilitate the development of web applications. It provides various functionalities that streamline the coding process for developers. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the fireasp package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access to sensitive data or enable other malicious activities. The issue was first identified 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 fireasp

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 fireasp package from your project until a secure version is released. You can do this by running the command: 'npm uninstall fireasp'. Alternatively, explore other packages that offer similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the fireasp package highlights the importance of maintaining secure coding practices and regularly updating dependencies. Users should take immediate action to mitigate risks associated with this vulnerability by uninstalling the package and monitoring for updates.

See every vulnerability recorded for fireasp →

Share this vulnerability

FAQ

The fireasp package is used for developing web applications in Node.js, providing various functionalities to streamline the coding process.

The malicious code was discovered through security assessments conducted by Amazon Inspector, which identified vulnerabilities in the fireasp package.

Using the fireasp package with malicious code can lead to unauthorized access to sensitive data, data breaches, and other security incidents.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

If you are using the fireasp package, it is recommended to uninstall it immediately and monitor for any updates or patches that address the vulnerability.

How To Fix

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

npm uninstall fireasp

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