Critical Malicious Code Vulnerability in @silgi/graphql Package

@silgi/graphql Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191314: Malicious code in @silgi/graphql (npm). Affects @silgi/graphql versions 0.7.15. 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 @silgi/graphql package is an npm library designed for building GraphQL APIs. It provides developers with tools to create efficient and flexible data-fetching mechanisms. However, this package has been compromised, leading to severe security risks for any application utilizing it.

Vulnerability Detail

The vulnerability originates from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This worm is capable of stealing tokens and credentials from the user's environment and publishing them to GitHub. It can also propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. The potential ramifications include complete compromise of the user's system, loss of sensitive data, and destruction of the user's home directory.

How To Fix

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

npm uninstall @silgi/graphql

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 you do not use the @silgi/graphql package in your projects. If you have already installed it, remove it and consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The @silgi/graphql package has been compromised, posing significant security risks to users. Immediate action is required to remove the package and secure any affected systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for @silgi/graphql →

Share this vulnerability

FAQ

Immediately uninstall the package using 'npm uninstall @silgi/graphql' and rotate any sensitive credentials stored on the affected machine.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

Failure to address this vulnerability can lead to complete system compromise, unauthorized access to sensitive data, and potential destruction of critical files.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

The malicious code was introduced by the Sha1-Hulud: The Second Coming NPM worm, which targets npm packages to steal credentials and propagate itself.

How To Fix

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

npm uninstall @silgi/graphql

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