Critical Malicious Code Vulnerability in csrengine Package

csrengine Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17787: Malicious code in csrengine (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The csrengine package is an npm library designed for managing and processing customer service requests. It provides functionalities that streamline customer interactions and automate responses. However, this package has been identified to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the csrengine package arises from the inclusion of malicious code that can compromise the security of applications using this library. This code can potentially lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall csrengine

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, users should consider removing the csrengine package from their projects until a secure version is released. This can be done by executing the command: npm uninstall csrengine.

Conclusion

The csrengine package has been identified to contain malicious code, posing a significant threat to applications that utilize it. Users are urged to update or remove the package to mitigate risks. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for csrengine →

Share this vulnerability

FAQ

The csrengine package is an npm library used for managing customer service requests and automating responses.

The malicious code can lead to unauthorized access and potential data breaches, affecting the security of applications.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities. Simply upload your package-lock.json file to check for vulnerabilities in real-time.

Currently, users are advised to update to the latest version of the csrengine package as soon as a patch is released.

If an immediate update is not possible, consider removing the csrengine package from your project as a temporary measure.

How To Fix

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

npm uninstall csrengine

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