Which versions of project-serum are malicious?

The following npm versions of project-serum are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate project-serum if I installed it?

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

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

Yes — project-serum is associated with the GHSA-p65m-h563-5vm7, RLMA-2025-05494, RLUA-2025-05919 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 project-serum 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 project-serum (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging project-serum across your stack and pipelines.

Malicious package

project-serumnpm

project-serum is a confirmed malicious npm package (MAL-2025-48340) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in project-serum (npm)

MAL-2025-48340

Immediate action

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

npm uninstall project-serum

What this malware does

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

1.0.0

Indicators of compromise (SHA-256)

0c390d6d9b15f1fb2c2ad9b8e802cff831ed02b6028b111d2937705df46f3fdc

865e9b4d15fa1a171bc627e806c81aaf69285f03824eb6a307cc38322e38ea43

dfa2593f27fc5f8962022d61e9fa402448ac372ffa1ed1a7116c271eabf4ffed

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

Campaign

GHSA-p65m-h563-5vm7RLMA-2025-05494RLUA-2025-05919

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks project-serum-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