Malicious Code Detected in fsd44 Package - Security Alert

fsd44 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21009: Malicious code in fsd44 (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 fsd44 package is an npm module that is utilized in various JavaScript applications for its specific functionalities. However, it has been identified as containing malicious code, posing a significant security risk to applications that depend on it. Users of this package should be aware of its vulnerabilities and take immediate action to protect their systems.

Vulnerability Detail

The fsd44 package has been found to harbor malicious code that can compromise the security of applications using it. This vulnerability originated from the package itself, which was introduced without proper scrutiny. The ramifications of this malicious code can include unauthorized access to sensitive data, data corruption, or even complete system takeover. It is crucial for developers to understand the risks associated with using this package and to take appropriate measures to mitigate them.

How To Fix

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

npm uninstall fsd44

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, you can replace the fsd44 package with an alternative package that provides similar functionality but does not have known vulnerabilities. Review your project's dependencies and consider using well-maintained packages from reputable sources.

Conclusion

The fsd44 package has been identified as containing malicious code, posing significant risks to applications that utilize it. Users are urged to remove the package and seek alternatives to safeguard their systems. Regular monitoring of dependencies is essential to maintain security.

See every vulnerability recorded for fsd44 →

Share this vulnerability

FAQ

The fsd44 package is an npm module used in JavaScript applications, but it has been flagged for containing malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you are using fsd44, you should remove it from your project immediately and look for alternative packages.

Currently, there is no patched version available for fsd44. It is advisable to remove the package until a secure alternative is found.

Using malicious packages can lead to unauthorized access to sensitive data, data corruption, and potential system breaches.

How To Fix

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

npm uninstall fsd44

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