Malicious Code Detected in core-get-started Package - Immediate Action Required

core-get-started Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17574: Malicious code in core-get-started (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 core-get-started package is a Node.js library designed to help developers quickly set up a basic project structure. It provides essential functionalities for initializing and managing project dependencies. However, this package has been found to contain malicious code, posing a significant risk to users who integrate it into their applications.

Vulnerability Detail

The vulnerability in the core-get-started package originates from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. Users must be aware that any version of this package from its inception (version 0) is affected, and immediate action is necessary to mitigate risks.

How To Fix

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

npm uninstall core-get-started

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, users can isolate the affected application from sensitive data and monitor its behavior closely. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The core-get-started package has been identified as containing malicious code, which poses serious security risks to applications that utilize it. Users are urged to take immediate action by removing the package and monitoring their applications for any unusual behavior. Utilizing tools like Vulert can aid in identifying vulnerabilities in your software.

See every vulnerability recorded for core-get-started →

Share this vulnerability

FAQ

The core-get-started package is a Node.js library that helps developers set up basic project structures quickly.

The malicious code can lead to unauthorized access and data breaches, posing significant security risks.

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

Currently, there is no patched version available. It is advised to remove the package and use secure alternatives.

Remove the core-get-started package from your project immediately and replace it with a secure alternative.

How To Fix

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

npm uninstall core-get-started

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