Which versions of corplib are malicious?

The following npm versions of corplib are flagged malicious: 1.0.0, 1.0.1, 2.0.0, 999.0.0. Treat any of these as compromised.

How do I remediate corplib if I installed it?

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

If 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.

Is corplib part of a known attack campaign?

Yes — corplib is associated with the RLMA-2025-06103 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find corplib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for corplib (4 malicious versions).

Malicious package

corplibnpm

Advisory published Dec 23, 2025Updated Dec 24, 2025

corplib is a confirmed malicious npm package (MAL-2025-192730) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 2.0.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in corplib (npm)

MAL-2025-192730

Immediate action

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

npm uninstall corplib

What this malware does

The package corplib was found to contain malicious code.

Malicious versions

4 flagged

1.0.01.0.12.0.0999.0.0

Indicators of compromise (SHA-256)

981b0f7adaff503c0e17de8e46c5fc6980d45fd37041570445c85bb44952a812

627fe2094fba9ae7d3dbeb480669a2b594428998d47e6f877f94e02eb513fe6f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06103

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks 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