Which versions of 4exepreds are malicious?

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

How do I remediate 4exepreds if I installed it?

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

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

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

Malicious package

4exepredsnpm

Advisory published Apr 2, 2026Updated Apr 7, 2026

4exepreds is a confirmed malicious npm package (MAL-2026-2434) 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 4exepreds (npm)

MAL-2026-2434

Immediate action

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

npm uninstall 4exepreds

What this malware does

The package 4exepreds was found to contain malicious code.

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

bb41a27c9bb4b46f750f96b9c501e4a8420852d3ea76be5cb5cd40896972cb0c

713fcab117c3d896c25c79498daded14d2b7d69baecb99c233703f421caaca26

Detection & response playbook

Malicious package

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