Malicious Code Detected in ci-queue Package - MAL-2025-17011

ci-queue Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17011: Malicious code in ci-queue (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 ci-queue package is a Node.js library used for managing and processing queues in asynchronous operations. It is designed to facilitate the handling of tasks in a structured manner, allowing developers to efficiently manage workloads in their applications. However, recent findings have revealed that this package contains malicious code, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the ci-queue package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may 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 to mitigate potential risks.

How To Fix

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

npm uninstall ci-queue

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 can remove the ci-queue package from their project until a secure version is released. This can be done by executing the following command: npm uninstall ci-queue. Alternatively, consider using an alternative package that provides similar functionality without the associated risks.

Conclusion

The ci-queue package has been identified as containing malicious code, which poses a significant risk to applications utilizing it. Users are strongly advised to update to a secure version or remove the package until a fix is available. Regular monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for ci-queue →

Share this vulnerability

FAQ

ci-queue is a Node.js library designed for managing asynchronous task queues in applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using the package.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Consider removing the ci-queue package from your project as a temporary measure until a secure version is available.

Vulert provides real-time monitoring and alerts for open-source vulnerabilities using just package-lock.json. Visit https://vulert.com for more details.

How To Fix

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

npm uninstall ci-queue

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