Malicious Code in gatsby-starter-gitlab (npm)

gatsby-starter-gitlab Updated 02 Oct 2025

Summary

05/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8431: Malicious code in gatsby-starter-gitlab (npm). Affects gatsby-starter-gitlab versions 1.0.0. 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 gatsby-starter-gitlab package is an npm package that serves as a starter template for creating Gatsby websites integrated with GitLab. It provides a foundation for building websites with features such as continuous deployment, version control, and collaboration. However, this package has been identified as containing malicious code.

Vulnerability Detail

The gatsby-starter-gitlab package has been flagged as malicious due to the following reasons:

  • The package communicates with a domain associated with malicious activity.
  • The package executes one or more commands associated with malicious behavior.

These actions indicate that the package may perform unauthorized activities or compromise the security of the system on which it is installed.

How To Fix

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

npm uninstall gatsby-starter-gitlab

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

There is no specific workaround provided for this vulnerability. It is essential to remove the package and take appropriate measures to secure your project.

Conclusion

The gatsby-starter-gitlab package has been identified as containing malicious code. It is recommended to remove this package from your project and review your code and dependencies for any other potential security risks. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for gatsby-starter-gitlab →

Share this vulnerability

FAQ

gatsby-starter-gitlab is an npm package that provides a starter template for creating Gatsby websites integrated with GitLab. It offers features such as continuous deployment and version control.

The OpenSSF Package Analysis project flagged the gatsby-starter-gitlab package as malicious based on its communication with a domain associated with malicious activity and the execution of commands linked to malicious behavior.

Using the gatsby-starter-gitlab package can expose your system to unauthorized activities and compromise its security. The malicious code may perform actions that could lead to data breaches, unauthorized access, or other malicious activities.

Yes, there are alternative packages and starter templates available for creating Gatsby websites integrated with GitLab. It is recommended to choose packages or templates from trusted sources and regularly review their security.

To ensure the security of your project, it is crucial to regularly review the packages and dependencies you use. Remove any packages flagged as malicious and keep your dependencies up to date. Additionally, consider implementing security measures such as code reviews, vulnerability scanning, and secure coding practices.

How To Fix

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

npm uninstall gatsby-starter-gitlab

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