Malicious Code Detected in draco-optimize-css-assets-webpack-plugin-proxima-nconf Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18729: Malicious code in draco-optimize-css-assets-webpack-plugin-proxima-nconf (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 draco-optimize-css-assets-webpack-plugin-proxima-nconf package is an npm module designed to optimize CSS assets in Webpack projects. It aims to enhance the performance of web applications by minimizing CSS file sizes. However, this package has been identified to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the draco-optimize-css-assets-webpack-plugin-proxima-nconf package. This code can potentially compromise the security of applications, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall draco-optimize-css-assets-webpack-plugin-proxima-nconf

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 packages that provide similar functionality without the associated risks. Review your package.json file and replace the draco-optimize-css-assets-webpack-plugin-proxima-nconf with a trusted CSS optimization plugin.

Conclusion

The draco-optimize-css-assets-webpack-plugin-proxima-nconf package has been identified as containing malicious code, posing a risk to applications that utilize it. It is crucial to remove this package and consider alternatives to ensure the security of your projects.

See every vulnerability recorded for draco-optimize-css-assets-webpack-plugin-proxima-nconf →

Share this vulnerability

FAQ

It is an npm module used for optimizing CSS assets in Webpack projects.

The malicious code was embedded in the package from its initial version, affecting all users who installed it.

Using this package can lead to security vulnerabilities, including unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall draco-optimize-css-assets-webpack-plugin-proxima-nconf

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