Which versions of fadlsjf are malicious?

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

How do I remediate fadlsjf if I installed it?

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

If fadlsjf was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is fadlsjf part of a known attack campaign?

Yes — fadlsjf is associated with the GHSA-34h2-gr5g-vc3j, RLMA-2026-01762, RLUA-2026-01947 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 fadlsjf across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fadlsjf (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fadlsjf across your stack and pipelines.

Malicious package

fadlsjfnpm

Malicious code in fadlsjf (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1948

Immediate action

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

npm uninstall fadlsjf

What this malware does

The package fadlsjf was found to contain malicious code.

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

5 flagged

1.0.01.0.11.0.21.0.31.0.4

Indicators of compromise (SHA-256)

84c2aa35dc6cdbc9581e9c90d31fc8048bf73c56102725c533f82882b2aa3422

7851237c54cc21d98214fdd4c10550fb6665672f78c6f685de666e25f116c54f

7f86b26743d0a98c6a13bbde4fbf078943448d1368cb9031ae14044c9cda491e

0118dc7e0772d16e9181e7ac4175faf6b8e203c0332c6411b02458772dd8a11f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fadlsjf (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fadlsjf across your stack and pipelines.
If you installed it — respond
Remove fadlsjf 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 fadlsjf was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks fadlsjf before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. fadlsjf on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-34h2-gr5g-vc3jRLMA-2026-01762RLUA-2026-01947

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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