Which versions of privy-farcaster-demo are malicious?

Every published version of privy-farcaster-demo on npm is considered malicious. Remove the package entirely.

How do I remediate privy-farcaster-demo if I installed it?

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

If privy-farcaster-demo 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.

How do I find privy-farcaster-demo across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for privy-farcaster-demo (all published versions).

Malicious package

privy-farcaster-demonpm

Advisory published Dec 1, 2025Updated Dec 1, 2025

privy-farcaster-demo is a confirmed malicious npm package (MAL-2025-191522) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in privy-farcaster-demo (npm)

MAL-2025-191522

Immediate action

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

npm uninstall privy-farcaster-demo

What this malware does

The package privy-farcaster-demo was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

87c7eee6179f85bcc2beaf0d3637f35c0a626b6db6222c86af862a01e01645e1

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks privy-farcaster-demo-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