Which versions of rollup-plugins-check are malicious?

The following npm versions of rollup-plugins-check are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate rollup-plugins-check if I installed it?

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

If rollup-plugins-check 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 rollup-plugins-check part of a known attack campaign?

Yes — rollup-plugins-check is associated with the IN-MAL-2026-014869, IN-MAL-2026-014867 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 rollup-plugins-check across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rollup-plugins-check (2 malicious versions).

Malicious package

rollup-plugins-checknpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

rollup-plugins-check is a confirmed malicious npm package (MAL-2026-12429) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rollup-plugins-check (npm)

MAL-2026-12429

Immediate action

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

npm uninstall rollup-plugins-check

What this malware does

The npm package [email protected] declares a postinstall script (node dist/module.js) that, on npm install, performs an HTTPS GET to https://workconfig.vercel.app with rejectUnauthorized: false and passes the response body to new Function('require', data)(require), executing the fetched code inside the installer's Node.js process with access to require. The remote body is opaque and controlled by whoever owns the endpoint; TLS certificate verification is explicitly disabled, so any on-path attacker can also substitute the payload. The package advertises itself as a rollup polyfill plugin and ships polyfill code copied from rollup-plugin-polyfill-node as cover, while the dropper is appended to the postinstall entry file. The name resembles the legitimate rollup-plugin-polyfill-node package.

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

2df0babe61716192dc900fc371f95e6b68d67568d680aa54b322a59688fbebeb

5f2c7fe6586c3734730d6f8cd5ffe893c3f7cc5ff82710d1f4df22b8e76987e8

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-014869IN-MAL-2026-014867

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks rollup-plugins-check-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