Malicious Code Detected in css-framework-test Package

css-framework-test Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17790: Malicious code in css-framework-test (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The css-framework-test package is an npm library designed for testing CSS frameworks. It is commonly used by developers to evaluate different styling options and frameworks in web development. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The css-framework-test package has been found to contain malicious code that can compromise the security of applications using it. This vulnerability originates from the package itself, which was introduced in version 0 and has not been addressed in subsequent releases. The malicious code can lead to unauthorized access, data breaches, or other harmful actions within the application environment.

How To Fix

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

npm uninstall css-framework-test

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

Currently, there are no specific workarounds to mitigate the effects of the malicious code in the css-framework-test package. The best approach is to uninstall the package entirely and replace it with a trusted alternative.

Conclusion

The css-framework-test package has been identified as containing malicious code, which poses serious security risks to applications. It is crucial to uninstall this package and replace it with a secure alternative to protect your application from potential threats.

See every vulnerability recorded for css-framework-test →

Share this vulnerability

FAQ

css-framework-test is an npm package used for testing various CSS frameworks in web development.

The specific nature of the malicious code has not been disclosed, but it poses significant security risks, including 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 if your application is affected without needing to sign up.

No, there is currently no patched version available for the css-framework-test package. It is advised to uninstall it.

You should uninstall the css-framework-test package immediately and consider using a secure alternative for your CSS framework testing.

How To Fix

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

npm uninstall css-framework-test

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