Critical Malicious Code Vulnerability in innocent-pkg Package

innocent-pkg Updated 20 Mar 2026

Summary

20/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1976: Malicious code in innocent-pkg (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 innocent-pkg package is an npm library designed for various utility functions in JavaScript applications. It is widely used due to its simplicity and ease of integration. However, it has been found to contain malicious code that compromises the security of any system where it is installed, making it a significant risk for developers and organizations relying on this package.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the innocent-pkg package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious code is designed to operate stealthily, making it difficult to detect and remove. Users are advised to treat any system with this package as compromised and to take 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 innocent-pkg

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 entirely and securing your system. It is essential to monitor your system for any signs of compromise after the removal.

Conclusion

The discovery of malicious code in the innocent-pkg package poses a serious threat to users and their systems. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for innocent-pkg →

Share this vulnerability

FAQ

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

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

No, there is currently no patched version available for innocent-pkg. The best course of action is to remove the package.

Failing to remove innocent-pkg can lead to unauthorized access to sensitive data and full control of your system by malicious actors.

No, it is highly recommended to avoid using innocent-pkg due to the embedded malicious code that compromises system security.

How To Fix

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

npm uninstall innocent-pkg

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