Malicious Code Vulnerability in stringify-coder Package

stringify-coder Updated 02 Dec 2025

Summary

01/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191588: Malicious code in stringify-coder (npm). Affects stringify-coder versions 3.0.2. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The stringify-coder package is a utility in the npm ecosystem that is designed to convert JavaScript objects into JSON strings. It is commonly used in web applications for data serialization. However, this package has been identified as having a serious vulnerability that allows for the execution of malicious code, potentially compromising the security of applications that rely on it.

Vulnerability Detail

The vulnerability in the stringify-coder package arises from the inclusion of malicious code in version 3.0.2. This code can execute arbitrary commands on the host system, leading to unauthorized access and data breaches. The source of this vulnerability has been traced back to a malicious actor who modified the package to include harmful scripts. The ramifications of this vulnerability are severe, as it can lead to data theft, system compromise, and loss of user trust.

How To Fix

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

npm uninstall stringify-coder

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

If immediate updating is not possible, consider removing the stringify-coder package from your project and replacing it with a more secure alternative until a patch is available.

Conclusion

The stringify-coder package has been compromised with malicious code, posing a significant risk to applications that utilize it. It is crucial to update to a secure version promptly to mitigate potential threats. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for stringify-coder →

Share this vulnerability

FAQ

stringify-coder is an npm package used for converting JavaScript objects into JSON strings, commonly utilized in web applications.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without any signup.

Failure to address this vulnerability can lead to unauthorized access, data breaches, and potential damage to your application's integrity and user trust.

Yes, updating to a secure version of the stringify-coder package will address the vulnerability. Use the command 'npm update stringify-coder' to update.

If you cannot update the package right away, consider removing it from your project and using a secure alternative until a patch is available.

How To Fix

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

npm uninstall stringify-coder

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