Critical Malicious Code Vulnerability in crpyto Package

crpyto Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17717: Malicious code in crpyto (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 crpyto package is an npm library designed for cryptographic operations, providing functionalities such as encryption and decryption. However, it has been identified to contain malicious code that can compromise user security. This vulnerability poses a significant risk to applications relying on this package for secure data handling.

Vulnerability Detail

The crpyto package has been found to harbor malicious code that can lead to unauthorized access and data breaches. This vulnerability originated from the package itself, which was compromised to include harmful scripts. Users of this package may face severe ramifications, including data theft and system exploitation, making it critical to address this issue promptly.

How To Fix

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

npm uninstall crpyto

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 temporary measure, you can avoid using the crpyto package and implement alternative libraries for cryptographic operations, such as 'crypto' or 'bcrypt'. Ensure to thoroughly test your application after making these changes.

Conclusion

The crpyto package has been identified as containing malicious code, posing significant risks to applications that utilize it. It is crucial to remove this package and consider alternatives to safeguard your application. Regular monitoring for vulnerabilities using tools like Vulert can help maintain security.

See every vulnerability recorded for crpyto →

Share this vulnerability

FAQ

The crpyto package is an npm library used for cryptographic functions, including encryption and decryption.

The package was found to contain malicious code that was intentionally introduced, posing security risks to users.

Using the compromised crpyto package can lead to unauthorized access, data breaches, and potential exploitation of your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall crpyto

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