Which versions of fngularjs are malicious?

The following npm versions of fngularjs are flagged malicious: 1.1.2, 1.1.4, 8.7.6. Treat any of these as compromised.

How do I remediate fngularjs if I installed it?

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

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

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

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

Malicious package

fngularjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

fngularjs is a confirmed malicious npm package (MAL-2026-7287) that executes malicious code on install (malicious versions 1.1.2, 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fngularjs (npm)

MAL-2026-7287

Immediate action

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

npm uninstall fngularjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

404c1b58a3ffe7627d09d7c853a0d54207832aea745e3f7a4848f6c8162929e1

30bef3fe86924a293ab593620bd9c5ac09f2436b0c17346f149b71c3083af17a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05092RLUA-2026-06245

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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