Critical Malicious Code Vulnerability in @t4i-cms-components/contact-card Package

Summary

12/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-209: Malicious code in @t4i-cms-components/contact-card (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 @t4i-cms-components/contact-card package is an npm library designed for integrating contact card functionalities into web applications. It allows developers to easily display and manage contact information. However, this package has been compromised, leading to severe security risks for any application utilizing it.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the @t4i-cms-components/contact-card package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it contains embedded malicious code that poses significant risks to users and systems.

How To Fix

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

npm uninstall @t4i-cms-components/contact-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 workaround, ensure that you do not use the @t4i-cms-components/contact-card package in your application. If you need similar functionality, consider using alternative packages that are verified and secure.

Conclusion

The @t4i-cms-components/contact-card package has been identified as containing malicious code that poses serious security risks. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for @t4i-cms-components/contact-card →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

No, there is currently no patched version of the @t4i-cms-components/contact-card package available.

Failing to address this vulnerability can lead to unauthorized access to sensitive information and complete compromise of the affected system.

It is highly recommended to avoid using the @t4i-cms-components/contact-card package altogether due to its malicious nature.

How To Fix

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

npm uninstall @t4i-cms-components/contact-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