Malicious Code Detected in pexels-internal Package - Security Risk Identified

pexels-internal Updated 02 Oct 2025

Summary

03/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6750: Malicious code in pexels-internal (npm). Affects pexels-internal versions >= 2.8.6. 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 pexels-internal package is an npm library designed for internal use, primarily facilitating access to Pexels' image and video resources. It is utilized in various applications to enhance media content. However, this package has been identified to communicate with a domain associated with malicious activities, posing a significant security risk to applications that rely on it.

Vulnerability Detail

The vulnerability arises from the package's communication with a domain linked to malicious activities, which can lead to data breaches, unauthorized access, or the execution of harmful code within the application. This issue was introduced in version 2.8.6, making it crucial for users of this version to take immediate action to mitigate potential threats.

How To Fix

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

npm uninstall pexels-internal

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

Conclusion

The pexels-internal package has a critical vulnerability that allows communication with a malicious domain, posing risks to applications using it. Users are advised to update or remove the package to ensure their applications remain secure.

See every vulnerability recorded for pexels-internal →

Share this vulnerability

FAQ

The pexels-internal package is an npm library used for accessing Pexels' media resources, primarily for internal applications.

The vulnerability involves communication with a domain associated with malicious activities, which can compromise application security.

You can use Vulert, which monitors open-source vulnerabilities in your software using just the package-lock.json file. Visit Vulert Scanner to check your application without any signup.

If an immediate update is not possible, consider removing the package temporarily to mitigate risks until a secure version is released.

The vulnerability was identified by Amazon Inspector, a security assessment service.

How To Fix

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

npm uninstall pexels-internal

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