Malicious Code Detected in asproject Package - Security Alert

asproject Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14935: Malicious code in asproject (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 asproject package is a Node.js library used for various project management tasks within the npm ecosystem. It is designed to facilitate project setup and management, providing developers with tools to streamline their workflow. However, it has recently been identified as containing malicious code, posing significant security risks to users who integrate it into their applications.

Vulnerability Detail

The vulnerability in the asproject package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, highlighting the importance of immediate action for users of this package.

How To Fix

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

npm uninstall asproject

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 asproject package from their project until a secure version is released. This can be done by executing the following command: 'npm uninstall asproject'. Consider using alternative packages that provide similar functionality without security risks.

Conclusion

The discovery of malicious code in the asproject package poses a serious threat to users. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Stay vigilant and utilize tools like Vulert to monitor your dependencies for any future vulnerabilities.

See every vulnerability recorded for asproject →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and may lead to data breaches or exploitation of the application.

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

Yes, you can utilize the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup or installation.

If immediate updates are not feasible, consider removing the package temporarily and looking for alternative solutions until a secure version is released.

Regularly check for updates from the maintainers of your packages and utilize tools like Vulert to receive real-time alerts about vulnerabilities.

How To Fix

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

npm uninstall asproject

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