Which versions of blots are malicious?

The following npm versions of blots are flagged malicious: 2.1.0, 2.1.1. Treat any of these as compromised.

How do I remediate blots if I installed it?

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

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

Yes — blots is associated with the IN-MAL-2026-011083, IN-MAL-2026-014901 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 blots across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for blots (2 malicious versions).

Malicious package

blotsnpm

Advisory published Jul 28, 2026Updated Aug 5, 2026

blots is a confirmed malicious npm package (MAL-2026-11158) that executes malicious code on install (malicious versions 2.1.0, 2.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in blots (npm)

MAL-2026-11158

Immediate action

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

npm uninstall blots

What this malware does

package.json defines preinstall and postinstall lifecycle scripts that unconditionally run curl against a hardcoded webhook.site endpoint, transmitting the installer's username (whoami), hostname, current working directory, and timestamp as query parameters. The endpoint is a third-party request-capture service controlled by the author (https://webhook.site/d80b4602-8a87-4693-8510-6ff77c62788e/blots). The package ships no other functionality tied to a documented purpose; the sole install-time effect is reconnaissance of the installer's host and identity to an attacker-controlled destination.

The OpenSSF Package Analysis project identified 'blots' @ 2.1.0 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

2.1.02.1.1

Indicators of compromise (SHA-256)

57066a6751b0444f7693ed35561fa24c16c649be8ce94c692b63f0470784866a

6e60effdc9b01c947156ba12242c977a67552eda460c939e41b3545603f45ccf

847ba592915f4561a16225808a93d2428bc12305dc3df0bbf5316bf5a5bd7518

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-011083IN-MAL-2026-014901

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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