Critical Malicious Code Vulnerability in theme-neutral Package

theme-neutral Updated 20 Jan 2026

Summary

20/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-371: Malicious code in theme-neutral (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 theme-neutral package is an npm library designed for theme management in web applications. It allows developers to create and manage themes efficiently, providing a flexible way to customize the appearance of applications. However, this package has been found to contain malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability originates from the theme-neutral package, which has been identified as containing embedded malicious code. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall theme-neutral

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

Conclusion

The theme-neutral package has a critical vulnerability due to embedded malicious code, which can compromise any system it is installed on. Immediate action is required to uninstall the package and secure sensitive information. Regular monitoring and using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for theme-neutral →

Share this vulnerability

FAQ

You should immediately uninstall the theme-neutral package and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected without needing to sign up.

The consequences include unauthorized access to sensitive data, potential data breaches, and loss of control over your systems.

No, there is currently no patch available for this vulnerability. The only solution is to uninstall the package.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall theme-neutral

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