Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@pumpfun-sdk/metadatanpm

@pumpfun-sdk/metadata is a confirmed malicious npm package (MAL-2025-47265) that executes malicious code on install (malicious versions 1.0.3, 1.0.4, 1.0.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @pumpfun-sdk/metadata (npm)

MAL-2025-47265
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @pumpfun-sdk/metadata

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

5 flagged
1.0.31.0.41.0.51.0.61.0.7

Indicators of compromise (SHA-256)

fe74efc7770fd428add3639b89ec07606c3be7a22d6c185ef00ad4beb39b9c15
2c34a483bc9e041a9ecf0e3709346e62809213b3628a314032107150d90870bb
8ecf620de70aec8aa1dd7f6ebc3ee796c2f69fc9097cb67bbb11072bdbaf5c8e
3f97af05c3030e594029a54701355e1bca19d10da41c7647f771b75dc41ea097
b252932a61aba6818ed70463f7d014165f7dbec271d77565fd85c1b286a0193e

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove @pumpfun-sdk/metadata 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.

  3. Did it already run?

    If @pumpfun-sdk/metadata 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.

  4. How O3 protects you

    O3 blocks @pumpfun-sdk/metadata 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. @pumpfun-sdk/metadata on npm has been identified as a malicious package (versions 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3583-g93h-v28gRLMA-2025-04857RLUA-2026-01048

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @pumpfun-sdk/metadata-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.

Explore

@pumpfun-sdk/metadata (npm) malicious package — MAL-2025-47265 | O3 Security