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

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

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

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

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

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

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

Malicious package

@gr-exports/asyncnpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

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

MAL-2025-191560

Immediate action

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

npm uninstall @gr-exports/async

What this malware does

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

Malicious versions

2 flagged

1.0.099.0.0

Indicators of compromise (SHA-256)

d00836e827e4c69be60729c4f8399d6132b3911b6ff017b19c7ec3bc77d6e1b1

b8832eae90b7d3651b42c92dfd4d5c51fa5766d1e571fab494f073a6389b3aa1

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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