Critical Malicious Code Vulnerability in typefence Package

typefence Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190936: Malicious code in typefence (npm). Affects typefence versions 1.2.2 – 1.2.3. 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 typefence package is an npm library designed to provide various functionalities for developers. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses significant risks, including unauthorized access to sensitive information and potential control over the affected system.

Vulnerability Detail

The vulnerability originates from the typefence package, which has been flagged as containing embedded malicious code. This code can lead to a complete compromise of any computer running the package, allowing attackers to access secrets and keys stored on the system. The ramifications of this vulnerability are severe, as it can result in unauthorized data access, system manipulation, and a breach of user privacy.

How To Fix

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

npm uninstall typefence

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

There are no effective workarounds for this vulnerability. The only recommended action is to remove the typefence package and secure the system by rotating any sensitive information.

Conclusion

The typefence package has been identified as containing malicious code that poses a significant security risk. Immediate removal of the package and rotation of any sensitive information is crucial to mitigate the impact of this vulnerability. Utilizing tools like Vulert can help monitor and alert for future vulnerabilities.

See every vulnerability recorded for typefence →

Share this vulnerability

FAQ

typefence is an npm package that provides various functionalities for developers but has been compromised with malicious code.

If you have the typefence package installed, your system is likely compromised. You should take immediate action to secure your system.

You should rotate all secrets and keys stored on the affected system from a different, secure computer.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall typefence

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