Critical Malicious Code Vulnerability in iron-github-io Package

iron-github-io Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5923: Malicious code in iron-github-io (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-github-io package is an npm library that is used for various functionalities related to GitHub integration. It is designed to facilitate interactions with GitHub's API, allowing developers to streamline their workflows. However, this package has been identified to contain malicious code that compromises the security of any system where it is installed, making it a significant threat to developers and organizations relying on it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the iron-github-io package. This code can lead to a complete compromise of the affected system, allowing unauthorized access to sensitive data, including secrets and keys. The malicious nature of the code means that any system running this package should be considered fully compromised, with potential ramifications including data theft, unauthorized access, and further exploitation of the system.

How To Fix

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

npm uninstall iron-github-io

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

There are no effective workarounds for this vulnerability other than removing the package and ensuring that your system is secure. It is advisable to monitor your system for any signs of compromise and take necessary actions to secure your environment.

Conclusion

The iron-github-io package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to uninstall the package and secure any compromised systems. Regular monitoring and evaluation of dependencies are essential to prevent similar vulnerabilities in the future.

See every vulnerability recorded for iron-github-io →

Share this vulnerability

FAQ

You should immediately uninstall the package using 'npm uninstall iron-github-io' and rotate any sensitive keys or secrets stored on your system.

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

Failing to address this vulnerability can lead to unauthorized access to your system, data theft, and potential exploitation of your environment.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.

While many npm packages are safe, it is crucial to evaluate the trustworthiness of packages before installation and to use tools like Vulert to monitor for vulnerabilities.

How To Fix

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

npm uninstall iron-github-io

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