Which versions of pro-express are malicious?

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

How do I remediate pro-express if I installed it?

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

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

Search your lockfiles and build artifacts for pro-express (version 1.0.0).

Malicious package

pro-expressnpm

Advisory published Apr 2, 2026Updated Apr 7, 2026

pro-express is a confirmed malicious npm package (MAL-2026-2445) 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 pro-express (npm)

MAL-2026-2445

Immediate action

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

npm uninstall pro-express

What this malware does

The package pro-express was found to contain malicious code.

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

c449b795f84201195315183f1bb5c85b932f39c9cce1260225aec17eee7c8344

508e68df7788049a51c684d3038db25fb043a5dda88579108c5eb49eacbfff95

Detection & response playbook

Malicious package

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