Critical Malicious Code Vulnerability in creats Package

creats Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17669: Malicious code in creats (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 creats package is an npm library designed for creating and managing various functionalities within JavaScript applications. It is widely used due to its ease of integration and robust features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the creats package, which was introduced in version 0. This malicious code can potentially compromise the security of applications, leading to unauthorized access, data breaches, or other harmful actions. Users of the package are at risk of exploitation if they do not take immediate action to mitigate this threat.

How To Fix

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

npm uninstall creats

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 remove the creats package from your project until a secure version is released. You can do this by executing: npm uninstall creats. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the creats package poses a serious threat to applications utilizing it. Immediate action is required to update or remove the package to safeguard against potential security breaches. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for creats →

Share this vulnerability

FAQ

The creats package is used for creating and managing functionalities in JavaScript applications, making it easier for developers to integrate various features.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected. Visit the Vulert playground at Vulert Scanner to check without any signup.

If immediate updates are not possible, consider removing the creats package from your project and using alternative packages until a secure version is available.

Using the creats package with this vulnerability can lead to unauthorized access, data breaches, and other security issues that can compromise your application and its users.

How To Fix

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

npm uninstall creats

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