Critical Malicious Code Vulnerability in fesenko Package

fesenko Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20418: Malicious code in fesenko (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 fesenko package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but its integrity has been compromised due to the presence of malicious code. This vulnerability poses a significant risk to applications relying on this package, as it can lead to unauthorized access or data manipulation.

Vulnerability Detail

The fesenko package was found to contain malicious code that can execute harmful actions within an application. This vulnerability originated from the introduction of malicious scripts in version 0 and has the potential to compromise user data, disrupt application functionality, and expose systems to further attacks. Users of this package are strongly advised to take immediate action to mitigate risks associated with this vulnerability.

How To Fix

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

npm uninstall fesenko

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 fesenko package altogether until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The fesenko package has been identified as containing malicious code, posing significant risks to applications that utilize it. Immediate action is required to remove the package and seek alternatives. Users are encouraged to monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for fesenko →

Share this vulnerability

FAQ

fesenko is an npm package used in JavaScript applications for various functionalities, but it has been compromised with 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 without signup.

Using the fesenko package can lead to unauthorized access, data manipulation, and potential system compromises due to the malicious code embedded within.

Currently, there is no patched version available. It is advisable to remove the package and look for secure alternatives.

If you have used fesenko in your project, you should remove it immediately and replace it with a secure alternative to mitigate any potential risks.

How To Fix

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

npm uninstall fesenko

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