Critical Malicious Code Vulnerability in jsonskipy Package

jsonskipy Updated 02 Oct 2025

Summary

08/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5703: Malicious code in jsonskipy (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 jsonskipy package is an npm library designed for JSON manipulation and processing. It is widely used in various JavaScript applications for its ease of use and efficiency in handling JSON data. However, it has been identified to contain malicious code that compromises the security of any system where it is installed, making it a significant risk for developers and organizations relying on this package.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the jsonskipy package. This code can lead to a complete compromise of the affected system, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code has been confirmed through various sources, indicating that any computer running this package should be considered fully compromised. The ramifications include potential data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall jsonskipy

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 for this vulnerability other than removing the package and ensuring that the system is secure. It is advisable to monitor the system for any unusual activity following the removal of the package.

Conclusion

The jsonskipy package has been identified as containing malicious code, posing a serious risk to any system where it is installed. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring and use of tools like Vulert can help in identifying such vulnerabilities in the future.

See every vulnerability recorded for jsonskipy →

Share this vulnerability

FAQ

jsonskipy is an npm library used for JSON manipulation and processing in JavaScript applications.

The vulnerability involves embedded malicious code that can compromise the security of any system where the package is installed.

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

Immediately remove the jsonskipy package and rotate any secrets or keys stored on the affected system.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

How To Fix

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

npm uninstall jsonskipy

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