Malicious Code Detected in api-facebooknew Package

api-facebooknew Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14642: Malicious code in api-facebooknew (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The api-facebooknew package is an npm library designed to facilitate interactions with Facebook's API. It provides developers with tools to integrate Facebook functionalities into their applications. However, this package has been identified as containing malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the api-facebooknew package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access to sensitive data, lead to data breaches, or enable other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall api-facebooknew

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 measure, developers can replace the functionality provided by the api-facebooknew package with alternative libraries that offer similar features without the associated risks. This may involve modifying the codebase to accommodate the new library.

Conclusion

The discovery of malicious code in the api-facebooknew package highlights the importance of vigilance in managing open-source dependencies. Users must take immediate action to mitigate risks by removing the affected package and monitoring for updates.

See every vulnerability recorded for api-facebooknew →

Share this vulnerability

FAQ

The api-facebooknew package is an npm library that allows developers to interact with Facebook's API for various functionalities.

The malicious code can potentially compromise application security, leading to unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

You should remove the package from your project immediately and consider using alternative libraries until a secure version is released.

Currently, there is no patched version available. Users are advised to remove the package until a secure update is released.

How To Fix

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

npm uninstall api-facebooknew

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