Critical Malicious Code Vulnerability in cryptopapi Package

cryptopapi Updated 20 Mar 2026

Summary

20/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1945: Malicious code in cryptopapi (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 cryptopapi package is an npm library designed for cryptographic operations, providing developers with tools to handle encryption and decryption tasks. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to users, as it can lead to unauthorized access and data breaches.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the cryptopapi package. This code can fully compromise any computer that has the package installed, allowing attackers to gain control over the system. As a result, all secrets and keys stored on the affected computer should be considered exposed and should be rotated immediately from a secure location. The malicious nature of this code falls under CWE-506, indicating that it embeds harmful functionality within the software.

How To Fix

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

npm uninstall cryptopapi

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, there are no effective workarounds to mitigate the risks posed by the cryptopapi package. The best course of action is to uninstall the package entirely and monitor your system for any signs of compromise.

Conclusion

The cryptopapi package has been identified as containing malicious code that poses a significant security risk. Users are strongly advised to uninstall the package immediately and take necessary precautions to secure their systems. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for cryptopapi →

Share this vulnerability

FAQ

You should uninstall the cryptopapi package immediately 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 by this vulnerability without needing to sign up.

Failing to remove the package may lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

After removing the package, you should rotate all secrets and keys from a secure environment to mitigate the impact of the compromise.

Vulert monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

How To Fix

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

npm uninstall cryptopapi

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