Malicious Code Detected in fenlaz Package - Security Alert

fenlaz Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20356: Malicious code in fenlaz (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 fenlaz package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and various features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the fenlaz package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue affects all versions starting from 0, 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 fenlaz

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 measure, consider removing the fenlaz package from your project until a secure version is released. You can do this by running the command: 'npm uninstall fenlaz'. This will help mitigate the risk while you await a fix.

Conclusion

The discovery of malicious code in the fenlaz npm package highlights the importance of regularly monitoring and updating dependencies in software projects. Users are urged to take immediate action to secure their applications by updating or uninstalling the affected package.

See every vulnerability recorded for fenlaz →

Share this vulnerability

FAQ

The fenlaz package is an npm library used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground.

If you cannot update the package right away, consider uninstalling it temporarily to reduce the risk of exploitation.

As of now, there is no patched version available. Keep an eye on the package repository for updates.

Using the compromised fenlaz package can lead to unauthorized access to your application, data breaches, and other malicious activities that can severely impact your project's security.

How To Fix

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

npm uninstall fenlaz

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