Critical Malicious Code Vulnerability in 4p9kgm Package

4p9kgm Updated 19 Oct 2026

Summary

19/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17948: Malicious code in 4p9kgm (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 4p9kgm package is a Node.js library available through npm, designed for various utility functions in JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses significant risks to users, as it can lead to unauthorized access and data breaches.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the 4p9kgm package. This code can fully compromise any computer that has the package installed, allowing an external entity to gain control over the system. The ramifications include potential data theft, unauthorized access to sensitive information, and the installation of additional malicious software. Users are advised to treat any system running this package as compromised and take immediate action to secure their data.

How To Fix

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

npm uninstall 4p9kgm

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

There are no effective workarounds for this vulnerability. The only recommended action is to uninstall the 4p9kgm package and secure the system.

Conclusion

The 4p9kgm package contains malicious code that poses a significant security risk to any system where it is installed. Users are strongly advised to uninstall the package immediately and secure their sensitive information. Continuous monitoring of dependencies is essential to prevent future vulnerabilities.

See every vulnerability recorded for 4p9kgm →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

No, there is currently no patched version available for the 4p9kgm package. The only solution is to uninstall it.

Failing to remove the package can lead to unauthorized access to your system, data breaches, and potential installation of additional malicious software.

Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

How To Fix

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

npm uninstall 4p9kgm

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