Malicious Code Detected in @mesh-components/card: A Critical Vulnerability

@mesh-components/card Updated 22 Mar 2026

Summary

22/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2022: Malicious code in @mesh-components/card (npm). Affects @mesh-components/card versions 99999.0.0. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package @mesh-components/card is a component library designed for building user interfaces in web applications. It provides various UI elements that developers can utilize to enhance the visual appeal and functionality of their applications. However, this package has been flagged for containing malicious code, which poses significant security risks to any application that integrates it.

Vulnerability Detail

The vulnerability in the @mesh-components/card package arises from its version 99999.0.0, which has been identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain linked to malicious activities and executes commands that can lead to unauthorized access or data breaches. This vulnerability can compromise the integrity of applications using this package, potentially allowing attackers to manipulate or steal sensitive information.

How To Fix

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

npm uninstall @mesh-components/card

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 measure, you can avoid using the @mesh-components/card package entirely until a secure version is released. If you need similar functionality, consider using alternative packages that have been vetted for security.

Conclusion

The @mesh-components/card package has been identified as containing malicious code, posing a significant threat to applications that utilize it. It is essential to take immediate action by updating or removing the package to safeguard your application from potential attacks. Utilizing tools like Vulert can help maintain awareness of vulnerabilities in your software dependencies.

See every vulnerability recorded for @mesh-components/card →

Share this vulnerability

FAQ

The package has been reported to communicate with a domain associated with malicious activities and execute harmful commands.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can identify if your application is affected. You can also check using the Vulert playground without any signup.

If an immediate update is not possible, consider removing the package and using alternative libraries that provide similar functionality without the associated risks.

While specific exploits have not been detailed, the nature of the malicious behavior suggests that attackers could leverage this vulnerability to gain unauthorized access or execute harmful actions within affected applications.

Regularly monitor your dependencies using tools like Vulert, which can provide real-time alerts for any vulnerabilities in your open-source packages.

How To Fix

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

npm uninstall @mesh-components/card

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