Malicious Code Detected in feature.genrator Package - Critical Security Alert

feature.genrator Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20346: Malicious code in feature.genrator (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The feature.genrator package is an npm library designed for generating features in applications. It is widely used due to its simplicity and efficiency in enhancing application functionality. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the feature.genrator package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall feature.genrator

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 feature.genrator package and look for alternative libraries that do not have known vulnerabilities. Additionally, you can monitor your project dependencies using tools like Vulert, which can help identify vulnerabilities in real-time without requiring access to the code or installation.

Conclusion

The discovery of malicious code in the feature.genrator package highlights the importance of monitoring dependencies in software projects. Users are advised to take immediate action by uninstalling the package and exploring alternative solutions to maintain the security of their applications.

See every vulnerability recorded for feature.genrator →

Share this vulnerability

FAQ

feature.genrator is an npm package used for generating features in applications, known for its ease of use.

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

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

You should uninstall the package immediately and look for alternative solutions to avoid security risks.

Currently, there is no patched version available. It is recommended to uninstall the package until a secure alternative is found.

How To Fix

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

npm uninstall feature.genrator

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