What does the web3-common malware do?

The OpenSSF Package Analysis project identified 'web3-common' @ 1.0.0 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

Which versions of web3-common are malicious?

The following npm versions of web3-common are flagged malicious: 1.0.0, 2.0.0. Treat any of these as compromised.

How do I remediate web3-common if I installed it?

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

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

Search your lockfiles and build artifacts for web3-common (2 malicious versions).

Malicious package

web3-commonnpm

Advisory published May 13, 2026Updated May 13, 2026

web3-common is a confirmed malicious npm package (MAL-2026-3718) that executes malicious code on install (malicious versions 1.0.0, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in web3-common (npm)

MAL-2026-3718

Immediate action

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

npm uninstall web3-common

What this malware does

The OpenSSF Package Analysis project identified 'web3-common' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

1.0.02.0.0

Indicators of compromise (SHA-256)

2e42f568897d9af194eb75275059455c99b369456b0c8e0ffe13e7f32be839e6

3836db7823a256da056db8f8cef16f8b4e4f62c9c6f21c99e16e3d8c0ef9a587

Detection & response playbook

Malicious package

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

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks web3-common-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