Critical Malicious Code Vulnerability in iron-selector Package

iron-selector Updated 10 Mar 2026

Summary

10/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1314: Malicious code in iron-selector (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 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 iron-selector package is a JavaScript library used in web development, particularly for creating custom elements and managing selection states in user interfaces. It is part of the npm ecosystem, which is widely utilized for package management in Node.js applications. This package allows developers to build interactive web components efficiently. However, it has recently been identified as containing malicious code, posing significant security risks to any application that incorporates it.

Vulnerability Detail

The vulnerability originates from the presence of malicious code embedded within the iron-selector package. This code can compromise any computer that has the package installed or running, granting unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it may lead to complete control of the affected system by an external entity. Users are advised to treat any system with this package as fully compromised, necessitating immediate action to secure their data.

How To Fix

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

npm uninstall iron-selector

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

Currently, the best workaround is to uninstall the iron-selector package and ensure that no remnants of the malicious code remain on your system. You can do this by running the following command in your terminal: 'npm uninstall iron-selector'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code within the iron-selector package poses a significant threat to users and their systems. Immediate action is required to mitigate risks, including uninstalling the package and securing sensitive information. Users are encouraged to stay informed about updates and consider using tools like Vulert for ongoing monitoring.

See every vulnerability recorded for iron-selector →

Share this vulnerability

FAQ

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

As of now, there is no patched version available. It is recommended to remove the package entirely.

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

It is not advisable to use the iron-selector package due to its compromised nature. Consider looking for alternative packages.

How To Fix

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

npm uninstall iron-selector

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