Critical Malicious Code Vulnerability in typescript-type-graphql Package

typescript-type-graphql Updated 18 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1540: Malicious code in typescript-type-graphql (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 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 typescript-type-graphql package is a popular library in the npm ecosystem that facilitates the creation of GraphQL APIs using TypeScript. It provides decorators and utilities that simplify the development process, allowing developers to define GraphQL schemas and resolvers in a type-safe manner. However, this package has been compromised, leading to severe security implications for any application utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the typescript-type-graphql package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this malicious code is linked to a specific commit identified by the SHA256 hash 1e725098035803e27c9f08511ac8bf72f1f7e4450ced4f3b0cb0abcd168a52c4. The ramifications of this vulnerability are dire, as it may lead to data breaches and unauthorized control over affected systems.

How To Fix

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

npm uninstall typescript-type-graphql

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 available for this vulnerability. The best course of action is to uninstall the affected package and monitor your system for any signs of compromise.

Conclusion

The typescript-type-graphql package has been compromised, posing a significant security risk to any system utilizing it. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring and vulnerability checks using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for typescript-type-graphql →

Share this vulnerability

FAQ

You should uninstall the package immediately 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. Visit Vulert Scanner to check your application without requiring any signup.

No, there is currently no patched version available for this package.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete control over your system by malicious actors.

It is highly discouraged to continue using this package due to the embedded malicious code. The safest option is to remove it entirely.

How To Fix

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

npm uninstall typescript-type-graphql

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