Which versions of seeds-random are malicious?

The following npm versions of seeds-random are flagged malicious: 2.3.7. Treat any of these as compromised.

How do I remediate seeds-random if I installed it?

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

If seeds-random 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 seeds-random part of a known attack campaign?

Yes — seeds-random is associated with the GHSA-w2qv-99v5-h3f5, RLMA-2025-06474, RLUA-2026-01555 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 seeds-random 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 seeds-random (version 2.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging seeds-random across your stack and pipelines.

Malicious package

seeds-randomnpm

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

MAL-2025-192315

Immediate action

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

npm uninstall seeds-random

What this malware does

The package seeds-random 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

1 flagged

2.3.7

Indicators of compromise (SHA-256)

47de9449cd7355e6e5c74ef85fbc39aceee380dfb0dbbb1f557dda15431d1ff6

795bbcfb5b0465693171101c152402cfb2b6c877bc4359dbb68b2844b905bcd9

aa5e6fad267ae26fe9d72055bade0a5429a0f89858a3005107756dca30dcca98

d74ca7a99c6792307509155ea7b37ed6b722606cb6ace0797ca014380ff1196b

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 seeds-random (version 2.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging seeds-random across your stack and pipelines.
If you installed it — respond
Remove seeds-random 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 seeds-random 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 seeds-random 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. seeds-random on npm has been identified as a malicious package (version 2.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w2qv-99v5-h3f5RLMA-2025-06474RLUA-2026-01555

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks seeds-random-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