Critical Malicious Code Vulnerability in fd4335 Package

fd4335 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20329: Malicious code in fd4335 (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 fd4335 package is an npm library that is utilized for various functionalities in JavaScript applications. It is designed to facilitate specific tasks within the ecosystem, but it has been identified as containing malicious code that compromises the integrity and security of applications utilizing it. This vulnerability poses a significant risk to developers and users relying on this package.

Vulnerability Detail

The fd4335 package has been found to contain malicious code, which can lead to unauthorized access, data breaches, or other harmful actions within an application. This vulnerability originated from the introduction of malicious code in version 0 and affects all subsequent versions. The ramifications can be severe, including potential exploitation by attackers to manipulate or steal sensitive information.

How To Fix

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

npm uninstall fd4335

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 avoid using the fd4335 package altogether and seek alternative libraries that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The fd4335 package has a critical vulnerability due to the presence of malicious code. It is crucial for developers to take immediate action by removing the package and replacing it with a secure alternative. Utilizing tools like Vulert can help in monitoring for vulnerabilities and ensuring the security of applications.

See every vulnerability recorded for fd4335 →

Share this vulnerability

FAQ

The fd4335 package is an npm library used in JavaScript applications for specific functionalities.

The fd4335 package contains malicious code that can compromise application security.

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

You should remove the fd4335 package and replace it with a secure alternative or update it if a patched version is available.

Vulert uses just the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall fd4335

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