Malicious Code Detected in common-styles Package - Security Alert

common-styles Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17432: Malicious code in common-styles (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The common-styles package is a widely used npm library that provides a set of common styles for web applications. It is designed to simplify the styling process and enhance the visual consistency of user interfaces. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that depend on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the common-styles package. This code can potentially compromise the security of applications that utilize the package, leading to unauthorized access, data breaches, or other malicious 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 common-styles

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, you can avoid using the common-styles package altogether and implement your own styling solutions or utilize other trusted styling libraries. This will help mitigate the risk associated with the malicious code.

Conclusion

The discovery of malicious code in the common-styles package highlights the importance of regularly monitoring and auditing dependencies in software projects. Developers are advised to take immediate action to remove the affected package and explore secure alternatives to safeguard their applications.

See every vulnerability recorded for common-styles →

Share this vulnerability

FAQ

The common-styles package is an npm library that provides a set of common styles for web applications, aimed at enhancing visual consistency.

The specific nature of the malicious code has not been disclosed, but it poses a risk of unauthorized access and data breaches.

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.

Currently, there is no patched version available. It is recommended to remove the package and look for alternatives.

You should remove the common-styles package from your project immediately and consider using alternative styling solutions.

How To Fix

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

npm uninstall common-styles

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