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

henriquedias Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171309: Malicious code in henriquedias (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 henriquedias package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These malicious packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for users relying on npm packages.

Vulnerability Detail

The vulnerability originates from the henriquedias package, which contains malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to the unintentional use of compromised packages by developers, potentially exposing their applications to further vulnerabilities and attacks.

How To Fix

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

npm uninstall henriquedias

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 henriquedias package and any packages that depend on it. Regularly audit your package-lock.json file to identify and remove any suspicious packages.

Conclusion

The henriquedias package poses a significant threat to npm users due to its malicious behavior of modifying package files and flooding the npm registry. It is essential to take immediate action by removing this package and ensuring that your project dependencies are secure. Utilizing tools like Vulert can help you monitor for vulnerabilities in real-time.

See every vulnerability recorded for henriquedias →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json file and can lead to the installation of compromised packages, which may introduce security vulnerabilities.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected by this vulnerability.

If you have installed henriquedias, you should uninstall it immediately using 'npm uninstall henriquedias' and audit your project for any other compromised packages.

There are no patches available for henriquedias as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall henriquedias

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