Which versions of expirs are malicious?

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

How do I remediate expirs if I installed it?

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

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

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

Malicious package

expirsnpm

Advisory published Apr 2, 2026Updated Apr 7, 2026

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

MAL-2026-2441

Immediate action

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

npm uninstall expirs

What this malware does

The package expirs was found to contain malicious code.

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

d82cf6807fa6c011a17d3f4e8bf8af1e3e935a3d79ab1420356fd87d3f2567de

86105842d926ee95e61ae8adf0d4506cbc55c9510189208ee33d511806f2c5ef

Detection & response playbook

Malicious package

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