Malicious Code Vulnerability in corp-sign-core-js Package

corp-sign-core-js Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1701: Malicious code in corp-sign-core-js (npm). Affects corp-sign-core-js versions 0.99.99 – 2.99.99. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The corp-sign-core-js package is a JavaScript library used in various applications for handling corporate signing functionalities. It is designed to streamline the process of digital signatures and document management. However, this package has been identified as having a critical vulnerability that allows for the injection of malicious code, potentially compromising the security of applications that utilize it.

Vulnerability Detail

The vulnerability in the corp-sign-core-js package arises from the presence of malicious code that can execute unauthorized actions within an application. This issue is attributed to specific versions of the package (0.99.99, 1.99.99, 2.99.99) that have been flagged by security researchers. The ramifications of this vulnerability include data breaches, unauthorized access to sensitive information, and potential exploitation by attackers. It is crucial for developers to address this vulnerability promptly to safeguard their applications.

How To Fix

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

npm uninstall corp-sign-core-js

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 versions of the corp-sign-core-js package from your project and replace them with an alternative library that provides similar functionality without the associated risks. Additionally, you can monitor your application using tools like Vulert to detect any vulnerabilities in real-time.

Conclusion

The corp-sign-core-js package has a critical vulnerability that can lead to serious security issues if not addressed. Developers are urged to update to the latest version and consider using monitoring tools like Vulert to ensure their applications remain secure.

See every vulnerability recorded for corp-sign-core-js →

Share this vulnerability

FAQ

The corp-sign-core-js package is a JavaScript library used for managing corporate digital signatures and document workflows.

The affected versions include 0.99.99, 1.99.99, and 2.99.99.

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

The consequences include unauthorized access to sensitive data, potential data breaches, and exploitation of the application by malicious actors.

You can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.

How To Fix

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

npm uninstall corp-sign-core-js

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