Which versions of raydium-bs58 are malicious?

Every published version of raydium-bs58 on npm is considered malicious. Remove the package entirely.

How do I remediate raydium-bs58 if I installed it?

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

If raydium-bs58 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is raydium-bs58 part of a known attack campaign?

Yes — raydium-bs58 is associated with the GHSA-qm27-pj7f-f7jh 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 raydium-bs58 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for raydium-bs58 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging raydium-bs58 across your stack and pipelines.

Malicious package

raydium-bs58npm

Malicious code in raydium-bs58 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2326

Immediate action

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

npm uninstall raydium-bs58

What this malware does

The package raydium-bs58 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

b6ba968c5cb1e12fc81fc5ed1694c2221b6ac0299199508b80100927801f07f3

866a59b63d949dfe36c6082c9daa6fddcb18993724e9980c245a49ff59944fee

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for raydium-bs58 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging raydium-bs58 across your stack and pipelines.
If you installed it — respond
Remove raydium-bs58 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 raydium-bs58 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks raydium-bs58 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. raydium-bs58 on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qm27-pj7f-f7jh

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks raydium-bs58-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