Which versions of @wbgo/shared are malicious?

The following npm versions of @wbgo/shared are flagged malicious: 0.0.1, 0.0.1-security, 99.9.10, 99.99.9, 99.99.10. Treat any of these as compromised.

How do I remediate @wbgo/shared if I installed it?

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

If @wbgo/shared 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 @wbgo/shared part of a known attack campaign?

Yes — @wbgo/shared is associated with the GHSA-qrfr-r945-w4v6, RLMA-2026-01077 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 @wbgo/shared across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @wbgo/shared (5 malicious versions).

Malicious package

@wbgo/sharednpm

Advisory published Jan 16, 2026Updated Mar 19, 2026

@wbgo/shared is a confirmed malicious npm package (MAL-2026-266) that executes malicious code on install (malicious versions 0.0.1, 0.0.1-security, 99.9.10…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @wbgo/shared (npm)

MAL-2026-266

Immediate action

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

npm uninstall @wbgo/shared

What this malware does

The package @wbgo/shared was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

5 flagged

0.0.10.0.1-security99.9.1099.99.999.99.10

Indicators of compromise (SHA-256)

fdb329e935e8aeef2d3a86a6d85a8b57f76574d7e339b3d50c0504601b9e67e1

98749f712baf86a5e8d0a6c22c6b6998a4decd916771550d27a31203104422f9

dbddccb04bee055a98fe2a0be56bdfcb712486b5e9dab19a55fe29cebd0aebce

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @wbgo/shared (5 malicious versions).
If you installed it — respond
Remove @wbgo/shared 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 @wbgo/shared 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. @wbgo/shared on npm has been identified as a malicious package (versions 0.0.1, 0.0.1-security, 99.9.10, 99.99.9, 99.99.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qrfr-r945-w4v6RLMA-2026-01077

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @wbgo/shared-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