Malicious Code Detected in genpkg: A Critical Vulnerability

genpkg Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21327: Malicious code in genpkg (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 genpkg package is an npm library designed for generating package files and managing dependencies in JavaScript applications. It is widely used due to its simplicity and efficiency in handling package configurations. However, recent findings have revealed that genpkg contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the genpkg 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 malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall genpkg

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, users can remove the genpkg package from their project until a secure version is released. This can be done by executing the command: 'npm uninstall genpkg'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the genpkg package highlights the importance of maintaining vigilance when using open-source libraries. Users are urged to update or remove the package to safeguard their applications from potential threats. Regular monitoring and assessment of dependencies are crucial in ensuring software security.

See every vulnerability recorded for genpkg →

Share this vulnerability

FAQ

genpkg is an npm package used for generating and managing package files in JavaScript applications.

The malicious code was identified through security assessments conducted by Amazon Inspector, which flagged the package for containing harmful elements.

Using genpkg with the malicious code can lead to unauthorized access to sensitive data, data breaches, and other security vulnerabilities.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. Visit https://vulert.com for more information.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall genpkg

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