Critical Malicious Code Vulnerability in shroom-kit Package

shroom-kit Updated 23 Jan 2026

Summary

21/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-428: Malicious code in shroom-kit (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 shroom-kit package is an npm library designed for various functionalities in JavaScript applications. It is commonly used for its ease of integration and utility features. However, it has been identified 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 malicious code embedded within the shroom-kit package. This code can lead to full compromise of any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The origins of this vulnerability have been traced back to two sources: Amazon Inspector and GHSA Malware reports, which confirm the malicious nature of the code. The ramifications of this vulnerability are severe, as it can lead to data breaches and unauthorized control over affected systems.

How To Fix

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

npm uninstall shroom-kit

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, there are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package and securing your system. Ensure that you monitor your systems for any unusual activity following the removal.

Conclusion

The shroom-kit package has been identified as containing malicious code that poses a significant risk to systems using it. Immediate action is required to remove the package and secure any sensitive information. Continuous monitoring for vulnerabilities is essential to maintain the security of your applications.

See every vulnerability recorded for shroom-kit →

Share this vulnerability

FAQ

shroom-kit is an npm package used in JavaScript applications for various utility functions.

The malicious code can lead to full system compromise, allowing unauthorized access to sensitive information.

Immediately remove the shroom-kit package and rotate all sensitive keys and secrets stored on your system.

As of now, there is no patched version available. The best course of action is to remove the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can also check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall shroom-kit

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