Critical Malicious Code Vulnerability in core-icon Package

core-icon Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17575: Malicious code in core-icon (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 core-icon package is an npm library designed to provide a set of icon components for web applications. It is widely used in various projects for its ease of integration and customizable features. However, recent findings have revealed that this package contains malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the core-icon package, which was introduced in version 0 and affects all subsequent versions. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the systems that rely on this package. Users of the core-icon package are strongly advised to take immediate action to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall core-icon

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 remove the core-icon package from your project until a secure version is available. This can be done by executing the following command: npm uninstall core-icon. Consider using alternative icon libraries that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the core-icon package poses a serious threat to applications that utilize it. Users are urged to update the package or remove it from their projects to safeguard their systems. Regular monitoring for vulnerabilities using tools like Vulert can help maintain application security.

See every vulnerability recorded for core-icon →

Share this vulnerability

FAQ

The core-icon package is an npm library that provides a collection of icon components for use in web applications.

The specific nature of the malicious code has not been disclosed, but it poses significant security risks, including unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Simply upload your package-lock.json file to check for vulnerabilities without needing to install any software.

Yes, it is recommended to update to the latest version of the core-icon package where the vulnerability has been addressed.

If immediate updates are not feasible, consider removing the package or using alternative libraries until a secure version is available.

How To Fix

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

npm uninstall core-icon

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