What does the corporate-blocking malware do?

The package corporate-blocking was found to contain malicious code. The OpenSSF Package Analysis project identified 'corporate-blocking' @ 2.99.99 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of corporate-blocking are malicious?

The following npm versions of corporate-blocking are flagged malicious: 2.99.99. Treat any of these as compromised.

How do I remediate corporate-blocking if I installed it?

Remove corporate-blocking from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed corporate-blocking — how do I know if it already compromised me?

If corporate-blocking was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find corporate-blocking across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for corporate-blocking (version 2.99.99).

Malicious package

corporate-blockingnpm

Advisory published Jan 22, 2026Updated Jan 23, 2026

corporate-blocking is a confirmed malicious npm package (MAL-2026-463) that executes malicious code on install (malicious version 2.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in corporate-blocking (npm)

MAL-2026-463

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall corporate-blocking

What this malware does

The package corporate-blocking was found to contain malicious code.

The OpenSSF Package Analysis project identified 'corporate-blocking' @ 2.99.99 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

2.99.99

Indicators of compromise (SHA-256)

fc6d759e06456e2ac7013ed6a7a36afea9e7a21ab6dc117937c5dd0d96b8d993

a096b32dfa76f7e64480d72862c34ec7e644ac03db51ad09af0eb1f929d637a1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for corporate-blocking (version 2.99.99).
If you installed it — respond
Remove corporate-blocking from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If corporate-blocking was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. corporate-blocking on npm has been identified as a malicious package (version 2.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks corporate-blocking-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database