Which versions of proleis-web-scanner are malicious?

The following npm versions of proleis-web-scanner are flagged malicious: 10.0.0, 10.1.0. Treat any of these as compromised.

How do I remediate proleis-web-scanner if I installed it?

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

If proleis-web-scanner 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.

Is proleis-web-scanner part of a known attack campaign?

Yes — proleis-web-scanner is associated with the RLMA-2026-01514 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find proleis-web-scanner across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for proleis-web-scanner (2 malicious versions).

Malicious package

proleis-web-scannernpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

proleis-web-scanner is a confirmed malicious npm package (MAL-2026-1828) that executes malicious code on install (malicious versions 10.0.0, 10.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in proleis-web-scanner (npm)

MAL-2026-1828

Immediate action

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

npm uninstall proleis-web-scanner

What this malware does

The package proleis-web-scanner was found to contain malicious code.

Malicious versions

2 flagged

10.0.010.1.0

Indicators of compromise (SHA-256)

0a0c428571105b71f21e10cf0850137d96da66bf940091b7ef5b90bdf84abfb9

99bb886b0dde88d16ff59ed346f20f0b69a299a33070c16def5b659ba308a3e8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for proleis-web-scanner (2 malicious versions).
If you installed it — respond
Remove proleis-web-scanner 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 proleis-web-scanner 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. proleis-web-scanner on npm has been identified as a malicious package (versions 10.0.0, 10.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01514

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks proleis-web-scanner-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