Malicious Code Injection in deploy-thread-scale-omega-enum Package

Summary

13/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-186561: Malicious code in deploy-thread-scale-omega-enum (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 deploy-thread-scale-omega-enum package is part of the npm ecosystem, primarily used for managing thread scaling in applications. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package, like others in the campaign, is designed to manipulate package metadata and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the deploy-thread-scale-omega-enum package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, polluting the npm registry and potentially compromising the integrity of dependent applications. The ramifications include the risk of unintentional use of compromised packages, leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall deploy-thread-scale-omega-enum

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 deploy-thread-scale-omega-enum package and replace it with a similar, trusted package that provides the same functionality without the associated risks.

Conclusion

The deploy-thread-scale-omega-enum package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the integrity and security of your applications.

See every vulnerability recorded for deploy-thread-scale-omega-enum →

Share this vulnerability

FAQ

It is an npm package used for managing thread scaling but has been identified as part of a malicious campaign.

The vulnerability can lead to the use of compromised packages, risking security breaches and data integrity.

You should uninstall the deploy-thread-scale-omega-enum package immediately and replace it with a trusted alternative.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without signing up.

How To Fix

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

npm uninstall deploy-thread-scale-omega-enum

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