Malicious Code Detected in alpha-9ly-project: A Critical npm Vulnerability

alpha-9ly-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14347: Malicious code in alpha-9ly-project (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 alpha-9ly-project is an npm package designed for various functionalities within JavaScript applications. It is commonly used for its ease of integration and utility in enhancing application performance. However, it has been identified to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the alpha-9ly-project arises from the inclusion of malicious code within the package. This code can lead to unauthorized access, data breaches, or other harmful actions that compromise the integrity of applications utilizing this package. The issue was introduced in version 0 and has been flagged as a serious security concern.

How To Fix

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

npm uninstall alpha-9ly-project

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 using alternative packages that provide similar functionalities without the associated risks. Evaluate your project's dependencies and replace the alpha-9ly-project with a trusted package.

Conclusion

The discovery of malicious code in the alpha-9ly-project npm package highlights the importance of maintaining secure dependencies in software development. Users are urged to take immediate action to mitigate risks associated with this vulnerability.

See every vulnerability recorded for alpha-9ly-project →

Share this vulnerability

FAQ

The alpha-9ly-project is an npm package used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

The risks include unauthorized access to sensitive data, potential data breaches, and the overall compromise of application security.

Currently, there is no specific patch version available. It is recommended to remove the package and look for alternatives.

Regularly audit your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall alpha-9ly-project

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