Which versions of expeedsxs are malicious?

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

How do I remediate expeedsxs if I installed it?

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

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

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

Malicious package

expeedsxsnpm

Advisory published Apr 2, 2026Updated Apr 7, 2026

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

MAL-2026-2438

Immediate action

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

npm uninstall expeedsxs

What this malware does

The package expeedsxs was found to contain malicious code.

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

a18b62a8149b23d84ea07608f7495ecd8a638cc1a476e821901b918b35303b39

d5cf76a69bccb5c0ce57cbf0552aaec481569fbfe1081d47aaf945567059ed4b

Detection & response playbook

Malicious package

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