Critical Malicious Code Vulnerability in style-postprocessor Package

style-postprocessor Updated 02 Oct 2025

Summary

28/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6334: Malicious code in style-postprocessor (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The style-postprocessor package is a Node.js library used for processing styles in web applications. It allows developers to manipulate and optimize CSS stylesheets efficiently. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, potentially leading to unauthorized access and data breaches.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the style-postprocessor package. This code can take full control of the affected system, allowing attackers to access sensitive information, such as secrets and keys. The ramifications of this vulnerability are severe, as any computer running this package should be considered fully compromised. The malicious code can persist even after the package is removed, making it critical for users to take immediate action.

How To Fix

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

npm uninstall style-postprocessor

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 workaround, users should avoid using the style-postprocessor package until a secure version is released. Additionally, consider using alternative packages for style processing that do not have known vulnerabilities.

Conclusion

The style-postprocessor package has a critical vulnerability due to embedded malicious code, posing significant risks to any system it is installed on. Immediate action is required to uninstall the package and secure sensitive information. Users are encouraged to monitor their applications for vulnerabilities using tools like Vulert.

See every vulnerability recorded for style-postprocessor →

Share this vulnerability

FAQ

The style-postprocessor package is a Node.js library designed for processing and optimizing CSS stylesheets in web applications.

The malicious code embedded in the style-postprocessor package can take full control of the affected system, allowing attackers to access sensitive information and potentially compromise the system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your application is affected by this vulnerability.

If you have the style-postprocessor package installed, you should uninstall it immediately and rotate any sensitive information stored on the affected system.

Yes, you can use Vulert's playground to monitor and check for vulnerabilities in your application without requiring any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall style-postprocessor

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