Malicious Code Exposure in makerjs-dev Package: A Critical Security Concern

makerjs-dev Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6939: Malicious code in makerjs-dev (npm). Affects makerjs-dev versions >= 1.1.1. 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 makerjs-dev package is an npm library designed for creating and manipulating 2D vector graphics in JavaScript. It provides developers with tools to generate SVG and other formats programmatically. However, this package has been identified as having a vulnerability that allows it to communicate with a domain associated with malicious activities, potentially compromising user data and application integrity.

Vulnerability Detail

The vulnerability in the makerjs-dev package originates from its ability to connect to a malicious domain. This connection can lead to unauthorized data access, data exfiltration, or even remote code execution, depending on the nature of the malicious activities associated with the domain. The issue was introduced in version 1.1.1, and it poses significant risks to applications relying on this package for vector graphics manipulation.

How To Fix

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

npm uninstall makerjs-dev

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 makerjs-dev package from your project until a secure version is released. Alternatively, you can implement network restrictions to block outgoing connections to the malicious domain associated with this package.

Conclusion

The makerjs-dev package has a critical vulnerability that allows communication with a malicious domain, posing significant risks to applications using it. It is essential to update the package to a secure version or implement workarounds to mitigate the risks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for makerjs-dev →

Share this vulnerability

FAQ

The makerjs-dev package is used for creating and manipulating 2D vector graphics in JavaScript, allowing developers to generate SVG and other formats programmatically.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help identify if your application is affected by this vulnerability.

If you cannot update the package, consider implementing network restrictions to block connections to the malicious domain or remove the package from your project until a secure version is available.

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

The potential consequences include unauthorized data access, data exfiltration, and remote code execution, which can compromise the security and integrity of your application.

How To Fix

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

npm uninstall makerjs-dev

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