What does the @mesh-helpers/common malware do?

The package @mesh-helpers/common was found to contain malicious code. The OpenSSF Package Analysis project identified '@mesh-helpers/common' @ 99999.0.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of @mesh-helpers/common are malicious?

The following npm versions of @mesh-helpers/common are flagged malicious: 99999.0.0. Treat any of these as compromised.

How do I remediate @mesh-helpers/common if I installed it?

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

If @mesh-helpers/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 @mesh-helpers/common across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @mesh-helpers/common (version 99999.0.0).

Malicious package

@mesh-helpers/commonnpm

Advisory published Mar 22, 2026Updated Mar 23, 2026

@mesh-helpers/common is a confirmed malicious npm package (MAL-2026-2021) that executes malicious code on install (malicious version 99999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @mesh-helpers/common (npm)

MAL-2026-2021

Immediate action

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

npm uninstall @mesh-helpers/common

What this malware does

The package @mesh-helpers/common was found to contain malicious code.

The OpenSSF Package Analysis project identified '@mesh-helpers/common' @ 99999.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99999.0.0

Indicators of compromise (SHA-256)

3c86cc06e9d97de0ef53ff01c2feee38bf1394e8a4db22e9ae19584fa8ad8f11

cb7b29c037fd6e505ddbd1506f78292b2b69aef43c5750ef655bb27d5dd9986e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @mesh-helpers/common (version 99999.0.0).
If you installed it — respond
Remove @mesh-helpers/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 @mesh-helpers/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. @mesh-helpers/common on npm has been identified as a malicious package (version 99999.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 @mesh-helpers/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