Malicious Code Detected in codegennativecomponent Package

codegennativecomponent Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17252: Malicious code in codegennativecomponent (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 codegennativecomponent package is an npm library designed for generating native components in JavaScript applications. It is utilized by developers to streamline the creation of native interfaces. However, this package has been found to contain malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the codegennativecomponent package arises from the inclusion of malicious code that can compromise the security of applications utilizing this library. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue originates from the package itself, which has been flagged as containing harmful elements that could exploit user data or system resources.

How To Fix

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

npm uninstall codegennativecomponent

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, consider removing the codegennativecomponent package from your project until a secure version is available. You can uninstall it using the command: 'npm uninstall codegennativecomponent'. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The discovery of malicious code in the codegennativecomponent package highlights the importance of maintaining secure dependencies in software development. It is crucial to stay updated with the latest patches and utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for codegennativecomponent →

Share this vulnerability

FAQ

The codegennativecomponent package is an npm library used for generating native components in JavaScript applications.

The malicious code found in the codegennativecomponent package can lead to unauthorized access and potential data breaches.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If you cannot update the package immediately, consider uninstalling it as a temporary measure to avoid exposure to the malicious code.

Yes, Vulert provides real-time monitoring for open-source vulnerabilities using just your package-lock.json file, allowing you to stay informed about potential risks.

How To Fix

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

npm uninstall codegennativecomponent

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