Which versions of fhgfhgfhfghhffhfgh are malicious?

The following npm versions of fhgfhgfhfghhffhfgh are flagged malicious: 11.11.11, 11.11.12. Treat any of these as compromised.

How do I remediate fhgfhgfhfghhffhfgh if I installed it?

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

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

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

Search your lockfiles and build artifacts for fhgfhgfhfghhffhfgh (2 malicious versions).

Malicious package

fhgfhgfhfghhffhfghnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

fhgfhgfhfghhffhfgh is a confirmed malicious npm package (MAL-2026-1739) that executes malicious code on install (malicious versions 11.11.11, 11.11.12). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fhgfhgfhfghhffhfgh (npm)

MAL-2026-1739

Immediate action

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

npm uninstall fhgfhgfhfghhffhfgh

What this malware does

The package fhgfhgfhfghhffhfgh was found to contain malicious code.

Malicious versions

2 flagged

11.11.1111.11.12

Indicators of compromise (SHA-256)

57b60d7c407b9a0c11d21df51dab920f0f16a874681477c4cb0aeafde6d9021f

072c555ec45dc90ccd215b5fe4227930590f00a42a5c155a356aa15369423816

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01318

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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