Which versions of fancode-web-app are malicious?

The following npm versions of fancode-web-app are flagged malicious: 99.0.0, 99.0.38. Treat any of these as compromised.

How do I remediate fancode-web-app if I installed it?

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

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

Yes — fancode-web-app is associated with the GHSA-f6pq-884h-rjxq, RLMA-2026-01948 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 fancode-web-app 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 fancode-web-app (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fancode-web-app across your stack and pipelines.

Malicious package

fancode-web-appnpm

Malicious code in fancode-web-app (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2130

Immediate action

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

npm uninstall fancode-web-app

What this malware does

The package fancode-web-app 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

2 flagged

99.0.099.0.38

Indicators of compromise (SHA-256)

a933e6c673f3cf2c4cb0e768570b64dcf627ac59e6b29c2e9afd5a5fb3d4396b

6e56c163153700b6fef7090e078a98b7c2403088e5c5f487344dc419af8adaa7

f96b90dd8bedb5b765cd5d9be2dd2c89676e1fd5a904fdf3dd7309da674913dc

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 fancode-web-app (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fancode-web-app across your stack and pipelines.
If you installed it — respond
Remove fancode-web-app 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 fancode-web-app 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 fancode-web-app 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. fancode-web-app on npm has been identified as a malicious package (versions 99.0.0, 99.0.38 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-f6pq-884h-rjxqRLMA-2026-01948

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks fancode-web-app-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