Malicious Code Detected in @measures/responsive: A Critical Vulnerability

@measures/responsive Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1630: Malicious code in @measures/responsive (npm). Affects @measures/responsive versions 99.99.9. 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 @measures/responsive package is a utility designed for responsive design measures in web applications, allowing developers to implement adaptive layouts easily. It is widely used in the npm ecosystem for its simplicity and effectiveness in managing responsive design elements. However, recent findings have identified a significant vulnerability within this package that exposes users to potential malicious code execution.

Vulnerability Detail

The vulnerability stems from malicious code embedded in version 99.99.9 of the @measures/responsive package. This code can lead to unauthorized access, data breaches, or other harmful actions within the user's environment. The origin of this malicious code is linked to a compromised package, which could have severe ramifications for any application relying on this version. Users are urged to take immediate action to mitigate risks associated with this vulnerability.

How To Fix

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

npm uninstall @measures/responsive

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, users can remove the affected package from their project until a secure version is confirmed. This can be done using the command: npm uninstall @measures/responsive. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the @measures/responsive package highlights the importance of maintaining vigilance in open-source software. Users must take proactive measures to secure their applications by updating or removing affected packages. Utilizing tools like Vulert can aid in monitoring vulnerabilities effectively.

See every vulnerability recorded for @measures/responsive →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can compromise the security of applications using the affected package.

You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without requiring any signup.

Immediately update the package to the latest version or uninstall it until a secure version is available.

Yes, the malicious code can lead to unauthorized access and potential data breaches, making it critical to address the vulnerability promptly.

Detailed information can be found in the vulnerability report on GitHub or through security advisories related to the @measures/responsive package.

How To Fix

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

npm uninstall @measures/responsive

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