Which versions of exszpe3szs are malicious?

The following npm versions of exszpe3szs are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate exszpe3szs if I installed it?

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

If exszpe3szs 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 exszpe3szs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for exszpe3szs (version 1.0.0).

Malicious package

exszpe3szsnpm

Advisory published Apr 2, 2026Updated Apr 7, 2026

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

Malicious code in exszpe3szs (npm)

MAL-2026-2444

Immediate action

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

npm uninstall exszpe3szs

What this malware does

The package exszpe3szs was found to contain malicious code.

The OpenSSF Package Analysis project identified 'exszpe3szs' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3bc14fbd9fa6d961f6b0e4e4b389e7aaefd494b9893d2e544178b2dc5f5e62f1

67f15551a64777edf23687b4e056220380ac9501b76e432e33f9d93f5aecf2d3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for exszpe3szs (version 1.0.0).
If you installed it — respond
Remove exszpe3szs 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 exszpe3szs 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. exszpe3szs on npm has been identified as a malicious package (version 1.0.0 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 exszpe3szs-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