Critical Malicious Code Vulnerability in f0klcr Package

f0klcr Updated 19 Oct 2026

Summary

19/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-18010: Malicious code in f0klcr (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 f0klcr package is an npm module that is utilized in various JavaScript applications for specific functionalities. However, it has been identified as containing malicious code that poses a significant security risk. This vulnerability can compromise the integrity of systems where the package is installed, leading to unauthorized access and data breaches.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the f0klcr package. Any system running this package is considered fully compromised, allowing attackers to gain control over the affected computer. This can lead to the exposure of sensitive information, including secrets and keys, which should be rotated immediately. The malicious nature of this code is classified under CWE-506, indicating that it contains code that appears to be harmful.

How To Fix

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

npm uninstall f0klcr

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 workaround, it is recommended to rotate all secrets and keys stored on the compromised computer from a secure, unaffected system. Additionally, ensure that no other malicious packages are present by conducting a thorough review of installed npm packages.

Conclusion

The f0klcr package poses a serious security threat due to the embedded malicious code it contains. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for f0klcr →

Share this vulnerability

FAQ

The f0klcr package is an npm module used in JavaScript applications, but it has been found to contain malicious code.

If you have the f0klcr package installed, your system is likely compromised. You can use tools like Vulert to monitor and alert for vulnerabilities.

Immediately remove the f0klcr package and rotate any sensitive information stored on the affected system.

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

Failing to address this vulnerability can lead to unauthorized access, data breaches, and potential control of your system by malicious actors.

How To Fix

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

npm uninstall f0klcr

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