Critical Malicious Code Vulnerability in crazytp Package

crazytp Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17660: Malicious code in crazytp (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 crazytp package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its unique features, but recent findings have revealed that it contains malicious code, posing significant risks to users and their applications. This vulnerability can lead to unauthorized access, data breaches, and other security issues.

Vulnerability Detail

The vulnerability in the crazytp package stems from the inclusion of malicious code that can compromise the integrity of applications utilizing this package. This code can execute harmful actions without the user's consent, potentially leading to data theft, system corruption, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall crazytp

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 workaround, you can avoid using the crazytp package altogether and look for alternative libraries that do not have known vulnerabilities. Always ensure to review the security status of any package before integrating it into your project.

Conclusion

The discovery of malicious code in the crazytp package highlights the importance of regularly reviewing and monitoring the security of open-source libraries. Users are advised to uninstall the package and seek alternatives to safeguard their applications.

See every vulnerability recorded for crazytp →

Share this vulnerability

FAQ

The crazytp package is an npm library used in JavaScript applications, but it has been found to contain malicious code.

The malicious code can execute unauthorized actions, leading to potential data breaches and system vulnerabilities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

You should uninstall the crazytp package immediately and look for alternative libraries that do not have security issues.

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

How To Fix

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

npm uninstall crazytp

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