Critical Malicious Code Vulnerability in alinaseh Package

alinaseh Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14313: Malicious code in alinaseh (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 alinaseh package is an npm library designed for various functionalities within JavaScript applications. It is utilized by developers for its ease of integration and utility features. However, it has been identified to contain malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the alinaseh 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 vulnerability was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall alinaseh

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 measure, users can remove the alinaseh package from their project until a secure version is released. This can be done by executing the command: npm uninstall alinaseh. Alternatively, consider using an alternative package that offers similar functionality without the associated risks.

Conclusion

The alinaseh package contains a critical vulnerability due to malicious code, which poses significant risks to applications. Users are urged to update or remove the package to safeguard their projects. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for alinaseh →

Share this vulnerability

FAQ

The alinaseh package is an npm library used for various functionalities in JavaScript applications, providing developers with utility features.

You can check if your application is affected by this vulnerability using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without any signup.

The malicious code can lead to unauthorized access, data breaches, and other harmful activities that compromise the integrity and security of your application.

Currently, there is no specific patch version mentioned. Users should monitor the package repository for updates and security fixes.

If immediate updates are not possible, consider removing the alinaseh package or using an alternative package until a secure version is available.

How To Fix

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

npm uninstall alinaseh

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