Malicious Code Detected in Ashore Package: A Critical Security Alert

ashore Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14903: Malicious code in ashore (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 Ashore package is a tool within the npm ecosystem designed to facilitate various functionalities for developers. It is commonly used for managing and deploying applications, providing a range of features that enhance productivity. However, recent findings have revealed that the package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the Ashore package stems from the inclusion of malicious code that can compromise the integrity of applications utilizing this package. This issue originated from a malicious actor who injected harmful scripts into the package, which can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The ramifications of this vulnerability are severe, as it can affect not only the immediate users of the package but also any applications that depend on it, leading to widespread security concerns.

How To Fix

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

npm uninstall ashore

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 Ashore package from their project until a secure version is confirmed. This can be accomplished by executing the command: 'npm uninstall ashore'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the Ashore package highlights the importance of vigilance in managing open-source dependencies. Users are urged to update their packages promptly and consider using tools like Vulert to monitor vulnerabilities in real-time. By taking these proactive steps, developers can safeguard their applications against potential threats.

See every vulnerability recorded for ashore →

Share this vulnerability

FAQ

Ashore is an npm package used for managing and deploying applications, offering various features to enhance developer productivity.

The malicious code can compromise application integrity, leading to unauthorized access and potential data breaches.

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

As a temporary measure, consider uninstalling the Ashore package and using alternative packages until a secure version is available.

Regularly check the package's repository and utilize tools like Vulert to receive alerts on open-source vulnerabilities.

How To Fix

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

npm uninstall ashore

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