Malicious Code Detected in entrypoint-paypal Package

entrypoint-paypal Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19676: Malicious code in entrypoint-paypal (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The entrypoint-paypal package is an npm library designed to facilitate interactions with PayPal's API, providing developers with tools to integrate payment processing into their applications. However, this package has been found to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the entrypoint-paypal package, which was introduced in version 0 and has the potential to compromise user data, execute unauthorized actions, or facilitate further attacks on the system. This malicious behavior can lead to severe ramifications for applications relying on this package, including data breaches and loss of user trust.

How To Fix

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

npm uninstall entrypoint-paypal

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, consider removing the entrypoint-paypal package from your project until a secure version is released. You can do this by executing: npm uninstall entrypoint-paypal.

Conclusion

The entrypoint-paypal package has been identified as containing malicious code, which poses serious security risks to applications using it. Users are advised to update the package or remove it until a secure version is available. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for entrypoint-paypal →

Share this vulnerability

FAQ

The entrypoint-paypal package is an npm library that allows developers to integrate PayPal payment processing into their applications.

The malicious code can compromise user data and execute unauthorized actions, posing significant security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Yes, updating to the latest version of the entrypoint-paypal package will help mitigate the vulnerability. Use 'npm update entrypoint-paypal' to update.

If an immediate update is not possible, consider uninstalling the package as a temporary measure to protect your application.

How To Fix

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

npm uninstall entrypoint-paypal

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