Which versions of @gr-exports/body are malicious?

The following npm versions of @gr-exports/body are flagged malicious: 1.0.0, 99.0.0. Treat any of these as compromised.

How do I remediate @gr-exports/body if I installed it?

Remove @gr-exports/body 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 @gr-exports/body — how do I know if it already compromised me?

If @gr-exports/body 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 @gr-exports/body part of a known attack campaign?

Yes — @gr-exports/body is associated with the RLMA-2025-05653 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 @gr-exports/body across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @gr-exports/body (2 malicious versions).

Malicious package

@gr-exports/bodynpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

@gr-exports/body is a confirmed malicious npm package (MAL-2025-191561) that executes malicious code on install (malicious versions 1.0.0, 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @gr-exports/body (npm)

MAL-2025-191561

Immediate action

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

npm uninstall @gr-exports/body

What this malware does

The package @gr-exports/body was found to contain malicious code.

Malicious versions

2 flagged

1.0.099.0.0

Indicators of compromise (SHA-256)

cf3805b51cf5491d9755dce541466f6a31e347a8ce66bb411fe85e0b31f670a9

d1ec75ab55ea86ba356e8f21309eb966c00366a526e9737edd15248594209f89

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05653

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @gr-exports/body-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