Malicious Code Detected in decoherence-loglevel-wezen-tailwindcss Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18162: Malicious code in decoherence-loglevel-wezen-tailwindcss (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 decoherence-loglevel-wezen-tailwindcss package is an npm library that integrates logging functionalities with Tailwind CSS styling. It is designed to enhance the development experience by providing a seamless way to manage logs while utilizing Tailwind's utility-first CSS framework. However, this package has been identified to contain malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the decoherence-loglevel-wezen-tailwindcss package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for developers to address this vulnerability promptly.

How To Fix

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

npm uninstall decoherence-loglevel-wezen-tailwindcss

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

As a temporary workaround, consider using alternative logging libraries that do not have known vulnerabilities. Additionally, ensure that your application is regularly monitored for any suspicious activities.

Conclusion

The decoherence-loglevel-wezen-tailwindcss package has been found to contain malicious code, posing serious security risks to applications. It is crucial for developers to take immediate action by uninstalling the package and monitoring their applications for any suspicious activities. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.

See every vulnerability recorded for decoherence-loglevel-wezen-tailwindcss →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications that utilize this package.

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.

You should uninstall the package immediately using npm uninstall decoherence-loglevel-wezen-tailwindcss and look for alternative solutions.

Currently, there is no patched version available. It is recommended to remove the package until a secure version is released.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to their latest versions.

How To Fix

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

npm uninstall decoherence-loglevel-wezen-tailwindcss

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