Critical Malicious Code Vulnerability in typescript-nhost Package

typescript-nhost Updated 18 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1552: Malicious code in typescript-nhost (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-nhost package is a JavaScript library designed for building serverless applications with TypeScript. It provides developers with tools to interact with Nhost services, including authentication, database management, and file storage. However, this package has been compromised, leading to significant security risks for any application utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the typescript-nhost package. This code can fully compromise any computer where the package is installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to a malicious actor who has embedded harmful code into the package, making it a severe threat to users and their systems.

How To Fix

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

npm uninstall typescript-nhost

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, consider using alternative packages that provide similar functionality without the associated risks. Always ensure to review the security status of any package before installation.

Conclusion

The typescript-nhost package has been compromised with malicious code, posing a significant risk to users. 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 typescript-nhost →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Currently, there is no patched version available for the typescript-nhost package.

Failing to address this vulnerability could lead to unauthorized access to sensitive data and full control of your system by malicious actors.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and always review package security before installation.

How To Fix

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

npm uninstall typescript-nhost

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