Malicious Code Detected in Corporate-Blocking Package: Version 2.99.99 Vulnerability

corporate-blocking Updated 22 Jan 2026

Summary

22/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-463: Malicious code in corporate-blocking (npm). Affects corporate-blocking versions 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The 'corporate-blocking' package is an npm library designed to manage corporate access restrictions in software applications. It aims to provide developers with tools to block or allow access to certain domains based on corporate policies. However, version 2.99.99 has been flagged for malicious behavior, raising concerns about its security and integrity.

Vulnerability Detail

The vulnerability in the 'corporate-blocking' package arises from its communication with a domain linked to malicious activities. Additionally, the package executes commands that are associated with harmful behavior, potentially compromising the security of applications that utilize it. This vulnerability poses significant risks, including unauthorized data access and system manipulation.

How To Fix

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

npm uninstall corporate-blocking

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 may consider removing the 'corporate-blocking' package from your project until a secure version is released. You can do this by running the command: npm uninstall corporate-blocking.

Conclusion

The 'corporate-blocking' package version 2.99.99 has been flagged for malicious behavior, posing significant security risks. It is essential to update or remove this package to safeguard your applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for corporate-blocking →

Share this vulnerability

FAQ

The 'corporate-blocking' package is an npm library used to manage access restrictions based on corporate policies.

Version 2.99.99 of the 'corporate-blocking' package has been identified as malicious.

The risks include unauthorized access to sensitive data and potential manipulation of the application’s functionality.

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

If immediate updates are not feasible, consider removing the package as a temporary measure until a secure version is available.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall corporate-blocking

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