Which versions of @sauravthakur/corplib are malicious?

Every published version of @sauravthakur/corplib on npm is considered malicious. Remove the package entirely.

How do I remediate @sauravthakur/corplib if I installed it?

Remove @sauravthakur/corplib 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 @sauravthakur/corplib — how do I know if it already compromised me?

If @sauravthakur/corplib 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 @sauravthakur/corplib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @sauravthakur/corplib (all published versions).

Malicious package

@sauravthakur/corplibnpm

Advisory published Nov 24, 2025Updated Nov 24, 2025

@sauravthakur/corplib is a confirmed malicious npm package (MAL-2025-190914) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sauravthakur/corplib (npm)

MAL-2025-190914

Immediate action

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

npm uninstall @sauravthakur/corplib

What this malware does

The package @sauravthakur/corplib was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

3ebf32bc4fe1000eb019415e2b1cbe68dcc9b52b3abb00d95d132ecb0740dde9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @sauravthakur/corplib (all published versions).
If you installed it — respond
Remove @sauravthakur/corplib 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 @sauravthakur/corplib 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. @sauravthakur/corplib on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @sauravthakur/corplib-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