Malicious Code Detected in emulate-slow-execute-try-small Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19638: Malicious code in emulate-slow-execute-try-small (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The 'emulate-slow-execute-try-small' package is an npm library designed to simulate slow execution for testing purposes. It is often used in development environments to mimic performance issues. However, this package has been found to contain malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the 'emulate-slow-execute-try-small' package. This code can potentially compromise the security of applications that depend on this package, leading to unauthorized access, data breaches, or other malicious activities. The issue is particularly concerning as it affects all versions starting from the initial release, 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 emulate-slow-execute-try-small

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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The 'emulate-slow-execute-try-small' package has been identified as containing malicious code, which poses a serious threat to applications that utilize it. Users are advised to remove the package and monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for emulate-slow-execute-try-small →

Share this vulnerability

FAQ

It is an npm package designed to simulate slow execution for testing purposes in development environments.

The specific nature of the malicious code has not been disclosed, but it poses security risks such as unauthorized access and data breaches.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

You should remove the package from your project immediately and look for alternative solutions.

Yes, you can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time.

How To Fix

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

npm uninstall emulate-slow-execute-try-small

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