Which versions of boby_parser are malicious?

The following npm versions of boby_parser are flagged malicious: 2.2.0, 2.2.2, 2.2.3. Treat any of these as compromised.

How do I remediate boby_parser if I installed it?

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

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

Yes — boby_parser is associated with the RLMA-2025-04466, RLUA-2025-05693 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 boby_parser across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for boby_parser (3 malicious versions).

Malicious package

boby_parsernpm

Advisory published Aug 14, 2025Updated Dec 2, 2025

boby_parser is a confirmed malicious npm package (MAL-2025-15924) that executes malicious code on install (malicious versions 2.2.0, 2.2.2, 2.2.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boby_parser (npm)

MAL-2025-15924

Immediate action

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

npm uninstall boby_parser

What this malware does

The package boby_parser was found to contain malicious code.

Malicious versions

3 flagged

2.2.02.2.22.2.3

Indicators of compromise (SHA-256)

ba2a1d616dacefe23c0d8b67fd76769bd2d9d91480a0f684adf8380f8bba5f6f

27b04e5dbe3ecfb8c414ab4247433b568f221755a2d21542001718ef6d4c5ec7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for boby_parser (3 malicious versions).
If you installed it — respond
Remove boby_parser 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 boby_parser 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. boby_parser on npm has been identified as a malicious package (versions 2.2.0, 2.2.2, 2.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04466RLUA-2025-05693

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks boby_parser-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