Malicious Code Injection in gabrielsilva Package: npm Vulnerability Summary

gabrielsilva Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171239: Malicious code in gabrielsilva (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The gabrielsilva 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 of applications by providing reusable code. 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 their applications.

Vulnerability Detail

The vulnerability originates from the gabrielsilva package being involved in a token reward campaign that floods the npm registry with malicious packages. These packages contain 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 compromise the integrity of the npm ecosystem and inflate developer reputation scores fraudulently.

How To Fix

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

npm uninstall gabrielsilva

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 gabrielsilva package and consider replacing it with a reputable alternative. You can also use tools like Vulert to monitor your project for vulnerabilities. To check if your application is affected by this vulnerability, you can use the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The gabrielsilva package poses a significant security risk due to its involvement in a malicious npm campaign. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for gabrielsilva →

Share this vulnerability

FAQ

The gabrielsilva package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

This vulnerability can compromise the integrity of your application by introducing malicious code that alters your package management and can lead to security breaches.

If you have installed the gabrielsilva package, you should uninstall it immediately using 'npm uninstall gabrielsilva' and monitor your project for any other vulnerabilities.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application using the Vulert playground at Vulert Scanner.

Yes, consider using reputable packages that provide similar functionality without the associated risks. Always verify the package's credibility before installation.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall gabrielsilva

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