Malicious Code Injection in typesens Package - Critical Security Risk

typesens Updated 05 Oct 2026

Summary

05/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17565: Malicious code in typesens (npm). Affects typesens versions 1.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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The typesens package is an npm library designed for utility functions, including a zod-based email-domain check. However, it has been found to contain malicious code that executes harmful scripts during installation. This vulnerability poses a significant risk to users who install the package, as it can lead to unauthorized access and control over their systems.

Vulnerability Detail

The vulnerability originates from the package.json file, which includes a postinstall script that executes 'wscript.exe 4444.vbs' upon installation. This script contains a multi-layer decryption mechanism that ultimately drops a malicious payload on the user's system. The payload is disguised as a legitimate telemetry aggregator, but it performs process hollowing using PowerShell, allowing attackers to execute arbitrary code. The obfuscation techniques used in the VBS script, such as randomized function names and XOR-decoding, make detection challenging.

How To Fix

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

npm uninstall typesens

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, avoid using the typesens package and consider using alternative libraries that provide similar functionality without the associated risks. Regularly audit your project's dependencies to ensure they are secure.

Conclusion

The discovery of malicious code in the typesens package highlights the importance of vigilance when using open-source libraries. Users should take immediate action to remove the affected package and monitor their systems for any unusual activity. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for typesens →

Share this vulnerability

FAQ

The typesens package is an npm library intended for utility functions, including email-domain validation. However, it has been compromised with malicious code.

The malicious code executes through a postinstall script in the package.json file, which runs a VBS script that drops harmful payloads on the system.

The risks include unauthorized access to the system, potential data breaches, and the ability for attackers to execute arbitrary code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Immediately uninstall the typesens package using 'npm uninstall typesens' and review your project for any other vulnerable dependencies.

How To Fix

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

npm uninstall typesens

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