Which versions of @metadata-ipfs/bonk.fun-ipfs are malicious?

The following npm versions of @metadata-ipfs/bonk.fun-ipfs are flagged malicious: 1.13.13, 1.13.14. Treat any of these as compromised.

How do I remediate @metadata-ipfs/bonk.fun-ipfs if I installed it?

Remove @metadata-ipfs/bonk.fun-ipfs 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 @metadata-ipfs/bonk.fun-ipfs — how do I know if it already compromised me?

If @metadata-ipfs/bonk.fun-ipfs 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 @metadata-ipfs/bonk.fun-ipfs part of a known attack campaign?

Yes — @metadata-ipfs/bonk.fun-ipfs is associated with the RLMA-2025-04327, RLUA-2026-01035 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 @metadata-ipfs/bonk.fun-ipfs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @metadata-ipfs/bonk.fun-ipfs (2 malicious versions).

Malicious package

@metadata-ipfs/bonk.fun-ipfsnpm

Advisory published Aug 28, 2025Updated Mar 19, 2026

@metadata-ipfs/bonk.fun-ipfs is a confirmed malicious npm package (MAL-2025-41450) that executes malicious code on install (malicious versions 1.13.13, 1.13.14). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @metadata-ipfs/bonk.fun-ipfs (npm)

MAL-2025-41450

Immediate action

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

npm uninstall @metadata-ipfs/bonk.fun-ipfs

Malicious versions

2 flagged

1.13.131.13.14

Indicators of compromise (SHA-256)

1f20a2eede805b4ccb40dd2de6452328ed31e04e1dd2b7f197fa6ed591dc4263

ecaa4c61835780108b80b961c512074965e025fdda438054b79f540a43978f7b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @metadata-ipfs/bonk.fun-ipfs (2 malicious versions).
If you installed it — respond
Remove @metadata-ipfs/bonk.fun-ipfs 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 @metadata-ipfs/bonk.fun-ipfs 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. @metadata-ipfs/bonk.fun-ipfs on npm has been identified as a malicious package (versions 1.13.13, 1.13.14 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04327RLUA-2026-01035

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @metadata-ipfs/bonk.fun-ipfs-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