Which versions of expeewas are malicious?

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

How do I remediate expeewas if I installed it?

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

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

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

Malicious package

expeewasnpm

Advisory published Apr 2, 2026Updated Apr 7, 2026

expeewas is a confirmed malicious npm package (MAL-2026-2439) 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 expeewas (npm)

MAL-2026-2439

Immediate action

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

npm uninstall expeewas

What this malware does

The package expeewas was found to contain malicious code.

The OpenSSF Package Analysis project identified 'expeewas' @ 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)

1139816aec09701aa03df7d77ec7cde1f0d119ecd358a6417dc28ad0f53cd99c

bcb3aafc860058ba4e9a64c6fa7dba85b7df72d68971ef7c673245e4ac02820f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for expeewas (version 1.0.0).
If you installed it — respond
Remove expeewas 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 expeewas 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. expeewas 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 expeewas-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