Critical Malicious Code Vulnerability in alinet Package

alinet Updated 16 Mar 2026

Summary

16/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1474: Malicious code in alinet (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 alinet package is a Node.js library available through npm, designed to facilitate various functionalities within JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to developers and organizations relying on this package for their projects.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the alinet package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems. Users are advised to treat any system with this package as compromised and take immediate action to secure their data.

How To Fix

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

npm uninstall alinet

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 workaround, if you need to maintain functionality while removing the alinet package, consider replacing it with a trusted alternative package that provides similar features. Always verify the integrity and security of any package before installation.

Conclusion

The alinet package poses a critical security risk due to embedded malicious code. Users must take immediate action to remove the package and secure their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for alinet →

Share this vulnerability

FAQ

Immediately uninstall the alinet package and rotate any sensitive information stored on the affected system.

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.

No, there is currently no patched version available for the alinet package. The only solution is to uninstall it.

Failing to remove the alinet package can lead to unauthorized access to sensitive data and complete compromise of your system.

Yes, but you will need to replace it with a secure alternative to maintain the desired functionality.

How To Fix

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

npm uninstall alinet

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