Malicious Code Detected in enum-sigma-test-double-container Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19678: Malicious code in enum-sigma-test-double-container (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 enum-sigma-test-double-container package is an npm library designed for testing purposes, allowing developers to create double containers for their applications. However, it has been identified to contain malicious code that poses a significant risk to users and their applications, potentially leading to unauthorized access or data breaches.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the enum-sigma-test-double-container package. This code can execute harmful actions without the user's consent, potentially compromising sensitive data or system integrity. The risk is particularly high for applications that rely on this package for testing, as it may inadvertently expose them to security threats.

How To Fix

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

npm uninstall enum-sigma-test-double-container

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 using alternative packages that provide similar functionality without the associated risks. Always ensure to review the package's reputation and user feedback before integrating it into your project.

Conclusion

The enum-sigma-test-double-container package has been found to contain malicious code, posing a significant risk to applications that utilize it. Users are advised to uninstall the package and consider alternatives while monitoring their projects for vulnerabilities.

See every vulnerability recorded for enum-sigma-test-double-container →

Share this vulnerability

FAQ

It is an npm library used for creating double containers in testing environments.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

The malicious code can lead to unauthorized access, data breaches, and potential exploitation of your application.

Currently, there is no specific patch for the affected version. It is recommended to uninstall the package or switch to a safer alternative.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated.

How To Fix

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

npm uninstall enum-sigma-test-double-container

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