Critical Malicious Code Vulnerability in turbo-json-parser Package

turbo-json-parser Updated 03 Mar 2026

Summary

03/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1213: Malicious code in turbo-json-parser (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 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 turbo-json-parser is an npm package designed for efficient JSON parsing. It is used in various applications to enhance performance when handling JSON data. However, this package has been compromised, leading to significant security concerns for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the turbo-json-parser 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 this code is classified under CWE-506, indicating that it contains embedded malicious code that poses a severe risk to users.

How To Fix

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

npm uninstall turbo-json-parser

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

Currently, the only effective workaround is to uninstall the turbo-json-parser package. This can be done using the command: npm uninstall turbo-json-parser. Ensure that all sensitive data is secured and rotated as necessary.

Conclusion

The turbo-json-parser package has been identified as containing malicious code that poses a significant threat to users. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in the future.

See every vulnerability recorded for turbo-json-parser →

Share this vulnerability

FAQ

The turbo-json-parser is an npm package used for efficient JSON parsing in applications.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to further security breaches.

Immediately uninstall the turbo-json-parser package and rotate any secrets or keys stored on the affected system.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities. You can check your application using the Vulert playground at Vulert Scanner without any signup.

While uninstalling the package is necessary, there is no guarantee that it will remove all malicious software that may have been installed as a result of the compromise.

How To Fix

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

npm uninstall turbo-json-parser

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