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

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

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

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

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

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

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

Malicious package

@gr-exports/headnpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

@gr-exports/head is a confirmed malicious npm package (MAL-2025-191562) 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/head (npm)

MAL-2025-191562

Immediate action

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

npm uninstall @gr-exports/head

What this malware does

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

Malicious versions

2 flagged

1.0.099.0.0

Indicators of compromise (SHA-256)

07953a5a160c0fd5a8a6b63a258533cb08c0bdd7a0fcc013475a87035b13756b

c6888eb30baaf533b512a0914e8563b29f47351f0154432f6c09fc209656ba10

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @gr-exports/head (2 malicious versions).
If you installed it — respond
Remove @gr-exports/head 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/head 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/head 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-05654

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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