Which versions of experedzss are malicious?

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

How do I remediate experedzss if I installed it?

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

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

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

Malicious package

experedzssnpm

Advisory published Apr 2, 2026Updated Apr 7, 2026

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

MAL-2026-2440

Immediate action

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

npm uninstall experedzss

What this malware does

The package experedzss was found to contain malicious code.

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

a93c7a3f654f6443a589bbeec7a013cfc4f478f2d86358be4252ec2e73e44433

f70a37180c88f0ddd0cc94346d4bb7703667321771ecc6de6c9c74f03a77f464

Detection & response playbook

Malicious package

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