Which versions of @gm-rvg/root-config are malicious?

The following npm versions of @gm-rvg/root-config are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate @gm-rvg/root-config if I installed it?

Remove @gm-rvg/root-config 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 @gm-rvg/root-config — how do I know if it already compromised me?

If @gm-rvg/root-config 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 @gm-rvg/root-config part of a known attack campaign?

Yes — @gm-rvg/root-config is associated with the GHSA-9crf-2vxq-9j4r, RLMA-2026-04725, RLUA-2026-05428 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 @gm-rvg/root-config across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @gm-rvg/root-config (version 99.9.1).

Malicious package

@gm-rvg/root-confignpm

Advisory published Jun 29, 2026Updated Jul 23, 2026

@gm-rvg/root-config is a confirmed malicious npm package (MAL-2026-6624) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @gm-rvg/root-config (npm)

MAL-2026-6624

Immediate action

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

npm uninstall @gm-rvg/root-config

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

439c6ce041ad5226eefdab8b99045e573701e66838e908be4fa6d3b0ee6e8a7b

2bf8ee4b0a67047f96665239a1a546646215d03edcb4827ffcc27aac3c3f15f6

cd46791e69863890bf79f2a2b91dc843a10f79ffeafeec7c384f47aeea32f766

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @gm-rvg/root-config (version 99.9.1).
If you installed it — respond
Remove @gm-rvg/root-config 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 @gm-rvg/root-config 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. @gm-rvg/root-config on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9crf-2vxq-9j4rRLMA-2026-04725RLUA-2026-05428

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @gm-rvg/root-config-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