Malicious Code Detected in artmatch Package - Security Alert

artmatch Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14879: Malicious code in artmatch (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 artmatch package is a Node.js library designed for image matching and manipulation. It provides developers with tools to perform various operations on images, making it a popular choice for applications that require image processing capabilities. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the artmatch package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code could potentially allow unauthorized access to sensitive data, execute arbitrary commands, or facilitate other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall artmatch

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, users can remove the artmatch package from their project until a secure version is available. This can be done by executing the following command: npm uninstall artmatch. Consider using alternative packages for image processing that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the artmatch package poses a serious threat to developers and their applications. Immediate action is required to mitigate risks by updating or removing the package. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for artmatch →

Share this vulnerability

FAQ

The artmatch package is used for image matching and manipulation in Node.js applications.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can identify if your application is affected by the artmatch vulnerability.

If you are using artmatch, it is recommended to uninstall the package immediately and look for alternative solutions until a secure version is released.

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

Using a compromised package can lead to unauthorized access to sensitive data, execution of malicious code, and potential breaches of your application's security.

How To Fix

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

npm uninstall artmatch

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