Malicious Code Injection in aimannaseem Package: A Threat to npm Users

aimannaseem Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170731: Malicious code in aimannaseem (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The aimannaseem package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package, like many others, is intended to facilitate development by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's package management system, leading to significant security concerns for developers and users alike.

Vulnerability Detail

The vulnerability originates from the aimannaseem package, which is associated with a broader malicious campaign targeting npm. This package contains scripts designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can inflate developer reputation scores fraudulently. This poses a risk of unintentional dependency on compromised packages, leading to potential data breaches or system vulnerabilities.

How To Fix

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

npm uninstall aimannaseem

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, you can avoid using the aimannaseem package and any packages that depend on it. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages. You can also use tools like Vulert to monitor your project for vulnerabilities without needing to access the code directly.

Conclusion

The aimannaseem package poses a significant security risk due to its malicious code designed to exploit the npm ecosystem. It is essential for developers to be vigilant, remove this package, and utilize tools like Vulert to monitor for vulnerabilities in their projects. Staying informed and proactive is key to maintaining a secure development environment.

See every vulnerability recorded for aimannaseem →

Share this vulnerability

FAQ

The aimannaseem package is an npm package that has been identified as part of a malicious campaign designed to exploit the npm registry.

This vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.

You should uninstall the aimannaseem package immediately and review your project dependencies for any other potentially compromised packages.

You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access. You can also check your application using the Vulert playground.

There is no patch for the aimannaseem package itself, as it is recommended to remove it entirely from your project.

How To Fix

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

npm uninstall aimannaseem

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