Critical Malicious Code Vulnerability in @client-web-next/origination-microfront Package

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16506: Malicious code in @client-web-next/origination-microfront (npm). Affects @client-web-next/origination-microfront versions 0.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 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 @client-web-next/origination-microfront package is a component of a web application that facilitates origination processes in a client-facing environment. It is built on the npm ecosystem and is designed to enhance user experience by providing seamless interactions. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @client-web-next/origination-microfront package. This code can potentially lead to unauthorized access, data breaches, or other malicious activities within the application. The issue was reported by ReversingLabs, and it affects version 0.0.1 of the package. The malicious code can execute harmful operations without the user's consent, making it imperative for developers to address this vulnerability promptly.

How To Fix

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

npm uninstall @client-web-next/origination-microfront

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 remove the affected package from your project by executing the following command: npm uninstall @client-web-next/origination-microfront. This will prevent the execution of the malicious code until a fix is implemented.

Conclusion

The @client-web-next/origination-microfront package has been identified with a critical vulnerability due to malicious code. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications. Regular monitoring for updates and utilizing tools like Vulert can help maintain security in open-source projects.

See every vulnerability recorded for @client-web-next/origination-microfront →

Share this vulnerability

FAQ

The malicious code can execute unauthorized actions within your application, potentially leading to data breaches or other security incidents.

You can use Vulert, which monitors and alerts for open-source vulnerabilities. Visit Vulert Scanner to check your application without requiring any signup.

Currently, there is no patched version available for the @client-web-next/origination-microfront package. It is advisable to monitor for updates.

If you cannot update the package, consider removing it from your project as a temporary measure to mitigate risks.

The vulnerability was reported by ReversingLabs, a cybersecurity firm specializing in threat detection.

How To Fix

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

npm uninstall @client-web-next/origination-microfront

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