Malicious Code in fca-kemdev (npm)

fca-kemdev Updated 02 Oct 2025

Summary

16/10/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8382: Malicious code in fca-kemdev (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 fca-kemdev package is an npm package that is used for a specific purpose in software development. It provides functionality related to fca-kemdev and is commonly used in various projects. However, this package has been found to contain malicious code, which poses a significant security risk to any computer that has it installed or running.

Vulnerability Detail

The malicious code in the fca-kemdev package has been identified as a serious security threat. Any computer with this package installed should be considered fully compromised. It is advised to rotate all secrets and keys stored on the affected computer immediately from a different computer. Although removing the package is recommended, it may not guarantee the removal of all malicious software that may have been installed as a result of its presence.

How To Fix

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

npm uninstall fca-kemdev

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

Unfortunately, there is no known workaround for this vulnerability. It is essential to follow the recommended steps for fixing the issue.

Conclusion

The fca-kemdev package has been found to contain malicious code, posing a significant security risk to any computer with it installed. It is crucial to take immediate action by rotating secrets and keys, removing the package, and conducting a security audit. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for fca-kemdev →

Share this vulnerability

FAQ

The fca-kemdev package is an npm package used in software development for a specific purpose.

The malicious code compromises the security of the affected computer, potentially granting control to an outside entity. All secrets and keys stored on the computer should be rotated immediately.

While removing the package is recommended, it does not guarantee the removal of all malicious software that may have been installed as a result of its presence. A thorough security audit is advised.

If you have the fca-kemdev package installed, it is crucial to rotate all secrets and keys stored on the affected computer immediately from a different, secure computer. Remove the package and conduct a security audit.

After removing the fca-kemdev package, it is recommended to conduct a thorough security audit to identify any potential damage or unauthorized access caused by the malicious code.

How To Fix

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

npm uninstall fca-kemdev

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