Malicious Code Detected in privy-farcaster-demo Package

privy-farcaster-demo Updated 01 Dec 2025

Summary

01/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191522: Malicious code in privy-farcaster-demo (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The privy-farcaster-demo package is an npm library designed for use in various JavaScript applications. It provides functionalities that may be leveraged for building decentralized applications. However, this package has been identified to contain malicious code, which poses a significant risk to users and their applications.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the privy-farcaster-demo package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The issue was identified by Amazon Inspector, which flagged the package for containing harmful elements that could exploit the system it runs on.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall privy-farcaster-demo

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can avoid using the privy-farcaster-demo package altogether until a secure version is released. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The privy-farcaster-demo package has been flagged for containing malicious code, posing a serious risk to applications that utilize it. Users are advised to uninstall the package and monitor for updates or consider alternative solutions until a secure version is available.

See every vulnerability recorded for privy-farcaster-demo →

Share this vulnerability

FAQ

The privy-farcaster-demo package is an npm library used for building decentralized applications in JavaScript.

The malicious code was detected by Amazon Inspector, which scans packages for security vulnerabilities.

Using the affected package can lead to unauthorized access, data breaches, and other security threats to your application.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall privy-farcaster-demo

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback