Which versions of r1dfg6789 are malicious?

The following npm versions of r1dfg6789 are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate r1dfg6789 if I installed it?

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

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

Yes — r1dfg6789 is associated with the RLMA-2026-01517 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 r1dfg6789 across my projects, lockfiles, and CI pipelines?

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

Malicious package

r1dfg6789npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

r1dfg6789 is a confirmed malicious npm package (MAL-2026-1830) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in r1dfg6789 (npm)

MAL-2026-1830

Immediate action

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

npm uninstall r1dfg6789

What this malware does

The package r1dfg6789 was found to contain malicious code.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

7731256a1133a477971cdf1dc2079cda7e992d561aa35f97103d04399a697b7c

cfae8a236efb920016a62dbf97522d7f2c6e6219bb3a3dbd6ca17680a2b0f83b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01517

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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