Critical Malicious Code Vulnerability in @aryanhussain/my-angular-lib Package

@aryanhussain/my-angular-lib Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190713: Malicious code in @aryanhussain/my-angular-lib (npm). Affects @aryanhussain/my-angular-lib versions 0.0.23. 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 @aryanhussain/my-angular-lib package is a JavaScript library designed for Angular applications, providing various functionalities to enhance development. However, this package has been identified as containing malicious code, posing significant risks to any system where it is installed. Users of this library should be aware of its potential to compromise sensitive data and system integrity.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @aryanhussain/my-angular-lib 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 ramifications include potential data breaches and loss of control over the affected systems. It is classified under CWE-506, indicating that the product contains code that appears to be malicious in nature.

How To Fix

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

npm uninstall @aryanhussain/my-angular-lib

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, ensure that the package is uninstalled using the command: npm uninstall @aryanhussain/my-angular-lib. Additionally, monitor your systems for any unusual activity and consider using security tools to scan for residual malicious software.

Conclusion

The discovery of malicious code in the @aryanhussain/my-angular-lib package poses a serious threat to users. Immediate action is required to mitigate risks, including uninstalling the package and securing sensitive information. Continuous monitoring and using tools like Vulert can help in identifying vulnerabilities in the future.

See every vulnerability recorded for @aryanhussain/my-angular-lib →

Share this vulnerability

FAQ

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

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Currently, there is no patched version available, so the best course of action is to remove the package entirely.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and potential control over your systems by malicious actors.

It is advisable to conduct thorough reviews and audits of any packages from the same author before using them, especially after discovering a serious vulnerability.

How To Fix

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

npm uninstall @aryanhussain/my-angular-lib

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