Malicious Code Detected in fusion-plugin-secure-headers: A Critical Security Alert

fusion-plugin-secure-headers Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21074: Malicious code in fusion-plugin-secure-headers (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 fusion-plugin-secure-headers package is an npm module designed to enhance security by managing HTTP headers in Fusion.js applications. It aims to provide developers with tools to implement security best practices effortlessly. However, this package has been identified to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the fusion-plugin-secure-headers package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other malicious activities. 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 fusion-plugin-secure-headers

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 fusion-plugin-secure-headers package from your project until a secure version is released. You can do this by executing the following command: npm uninstall fusion-plugin-secure-headers. This will help mitigate the risk of malicious code execution in your application.

Conclusion

The discovery of malicious code in the fusion-plugin-secure-headers package highlights the importance of maintaining vigilance in open-source software. Users are encouraged to update or uninstall the package to safeguard their applications from potential threats.

See every vulnerability recorded for fusion-plugin-secure-headers →

Share this vulnerability

FAQ

It is an npm module designed to help developers manage HTTP security headers in Fusion.js applications.

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

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

Yes, it is recommended to update the package to the latest secure version as soon as it is released.

As a temporary measure, you should uninstall the package to prevent any potential exploitation of the vulnerability.

How To Fix

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

npm uninstall fusion-plugin-secure-headers

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