Malicious Code Injection in hassanraza Package: npm Vulnerability Overview

hassanraza Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171304: Malicious code in hassanraza (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 hassanraza package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the hassanraza package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify package.json files, removing private flags and altering version numbers. The malicious payload generates random package names and continuously republishes variants, which can lead to pollution of the npm registry and compromise developer reputation scores. This behavior poses significant risks, including the potential for unintentional code execution and dependency confusion.

How To Fix

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

npm uninstall hassanraza

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, avoid using the hassanraza package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your project's dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The hassanraza package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for hassanraza →

Share this vulnerability

FAQ

The hassanraza package is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.

The malicious code can modify your package.json file, remove private flags, and publish unauthorized versions, leading to potential security risks.

You should uninstall the hassanraza package immediately using 'npm uninstall hassanraza' and check for any alternative packages.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall hassanraza

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