Malicious Code Detected in appmake: A Critical Security Alert

appmake Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14730: Malicious code in appmake (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The appmake package is an npm library designed for application development, providing various utilities to streamline the app creation process. However, it has been identified to contain malicious code that poses significant security risks to users and their applications. This vulnerability can lead to unauthorized access or data breaches, making it crucial for developers to address it promptly.

Vulnerability Detail

The vulnerability in the appmake package originates from the inclusion of malicious code, which can compromise the integrity of applications that utilize this package. The malicious code can execute harmful actions without the user's consent, potentially leading to data theft or system exploitation. This issue affects all versions starting from 0, making it imperative for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall appmake

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 appmake package from your project until a secure version is released. You can uninstall it using the command: 'npm uninstall appmake'.

Conclusion

The discovery of malicious code in the appmake package highlights the importance of maintaining secure dependencies in software development. Users are urged to update or remove the affected package to safeguard their applications against potential threats.

See every vulnerability recorded for appmake →

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions within applications, potentially leading to data breaches or system vulnerabilities.

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

As a temporary measure, you should uninstall the appmake package to prevent any potential exploitation until a secure version is available.

Yes, tools like Vulert can help you monitor your package-lock.json file for vulnerabilities in real-time.

Failing to address this vulnerability could lead to unauthorized access to sensitive data, application downtime, or further exploitation of your system.

How To Fix

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

npm uninstall appmake

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