Malicious Code Detected in ing-feat-kyc-consent Package - Security Risk Identified

ing-feat-kyc-consent Updated 25 Dec 2025

Summary

25/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192934: Malicious code in ing-feat-kyc-consent (npm). Affects ing-feat-kyc-consent versions 99.99.99. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'ing-feat-kyc-consent' package is a Node.js library available via npm, designed to facilitate Know Your Customer (KYC) consent processes in applications. It is utilized for managing user consent in compliance with regulatory requirements. However, this package has been flagged for malicious activity, raising concerns about its integrity and security.

Vulnerability Detail

The vulnerability in the 'ing-feat-kyc-consent' package stems from its communication with a domain known for malicious activities and the execution of commands that are associated with harmful behavior. This poses significant risks, including unauthorized data access, potential data breaches, and exploitation of user systems. The package version identified as malicious is 99.99.99, and it has been flagged by the OpenSSF Package Analysis project.

How To Fix

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

npm uninstall ing-feat-kyc-consent

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 measure, you can avoid using the 'ing-feat-kyc-consent' package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'ing-feat-kyc-consent' package has been identified as malicious, posing significant security risks. It is essential to take immediate action to remove the affected version and monitor for updates. Utilizing tools like Vulert can help in real-time monitoring of vulnerabilities in your software.

See every vulnerability recorded for ing-feat-kyc-consent →

Share this vulnerability

FAQ

It is a Node.js library used for managing KYC consent processes in applications.

It communicates with a domain linked to malicious activities and executes harmful commands.

Risks include unauthorized data access, potential data breaches, and exploitation of user systems.

You can use Vulert's playground at Vulert Scanner to monitor and alert for vulnerabilities in your application without requiring any signup.

Remove the affected version and update to the latest secure version if available.

How To Fix

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

npm uninstall ing-feat-kyc-consent

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