Malicious code in u-workflow.components (npm)

u-workflow.components Updated 02 Oct 2025

Summary

25/06/2024
CRITICAL
No i
Critical
Not published

MAL-2024-3247: Malicious code in u-workflow.components (npm). Affects u-workflow.components versions 1.0.0. 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 u-workflow.components package is an npm package that provides components for workflow management in JavaScript applications. It is commonly used to streamline and automate various business processes. However, this package has been found to contain malicious code, posing a security risk to applications that utilize it.

Vulnerability Detail

The vulnerability (MAL-2024-3247) originates from a specific version (1.0.0) of the u-workflow.components package. The malicious code was discovered by ReversingLabs and reported through the Open Source Vulnerability (OSV) format. The code's intent and potential ramifications are not specified in the provided information, but it is crucial to address this issue promptly to prevent any potential harm to affected applications.

How To Fix

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

npm uninstall u-workflow.components

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

No workaround has been provided for this vulnerability. It is essential to rely on the official fix provided by the package maintainers.

Conclusion

The u-workflow.components package has been found to contain malicious code, posing a security risk to applications that use it. It is crucial to update to a secure version of the package as soon as it becomes available to mitigate this vulnerability.

See every vulnerability recorded for u-workflow.components →

Share this vulnerability

FAQ

u-workflow.components is an npm package that offers components for workflow management in JavaScript applications. It helps streamline and automate business processes.

The impact of this vulnerability is not specified in the provided information. However, it is crucial to address it promptly to prevent any potential harm to affected applications.

This vulnerability was discovered by ReversingLabs, a security research firm.

To fix this vulnerability, update the u-workflow.components package to a secure version that does not contain the malicious code. Keep an eye on official announcements from the package maintainers for a patched version.

No workaround has been provided for this vulnerability. Rely on the official fix from the package maintainers.

How To Fix

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

npm uninstall u-workflow.components

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