Malicious Code Detected in indexer-worker-service: A Critical Vulnerability

indexer-worker-service Updated 02 Oct 2025

Summary

21/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6098: Malicious code in indexer-worker-service (npm). Affects indexer-worker-service versions >= 1.0.1. 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 indexer-worker-service is an npm package designed for indexing and processing data efficiently. It is commonly used in applications that require background processing and task management. However, this package has been found to communicate with a domain associated with malicious activities, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the package's communication with a malicious domain, which can lead to unauthorized data access, data manipulation, or even remote code execution. This issue is particularly concerning as it can compromise the integrity and confidentiality of the application and its users. The vulnerability was introduced in version 1.0.1 of the package, making it crucial for users to be aware of the risks associated with this version.

How To Fix

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

npm uninstall indexer-worker-service

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, consider removing the indexer-worker-service package from your project until a secure version is released. Alternatively, you can implement network restrictions to block communication with the malicious domain, although this may affect the functionality of the package.

Conclusion

The indexer-worker-service package has a critical vulnerability due to its communication with a malicious domain. It is essential for developers using this package to update to a secure version and monitor their applications for potential threats. Utilizing tools like Vulert can aid in maintaining the security of your software.

See every vulnerability recorded for indexer-worker-service →

Share this vulnerability

FAQ

The indexer-worker-service is an npm package used for background data indexing and processing tasks in applications.

The vulnerability can lead to unauthorized access to sensitive data, data manipulation, or remote code execution, compromising your application's security.

If you are using version 1.0.1, it is crucial to update to a patched version as soon as possible to mitigate the risks associated with this vulnerability.

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall indexer-worker-service

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