Malicious Code Detected in generator-sglk Package - Immediate Action Required

generator-sglk Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21303: Malicious code in generator-sglk (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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The generator-sglk package is an npm tool designed for scaffolding projects, providing developers with a streamlined way to set up new applications. However, it has been identified to contain malicious code, posing significant security risks to users who integrate it into their projects. This vulnerability can lead to unauthorized access or manipulation of sensitive data within applications that utilize this package.

Vulnerability Detail

The vulnerability in the generator-sglk package stems from the inclusion of malicious code that can compromise the integrity and security of applications using it. This code can potentially allow attackers to execute arbitrary commands, steal sensitive information, or disrupt application functionality. The malicious nature of this vulnerability was confirmed by Amazon Inspector, highlighting the urgent need for users to address this issue.

How To Fix

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

npm uninstall generator-sglk

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

If an immediate update is not feasible, consider removing the generator-sglk package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall generator-sglk'.

Conclusion

The discovery of malicious code in the generator-sglk package poses a serious threat to developers and their applications. Immediate action is required to update or remove the package to safeguard against potential attacks. Utilizing tools like Vulert can help monitor your projects for vulnerabilities in real-time.

See every vulnerability recorded for generator-sglk →

Share this vulnerability

FAQ

generator-sglk is an npm package used for scaffolding projects, helping developers quickly set up new applications.

The malicious code can allow unauthorized access to sensitive data and may enable attackers to execute arbitrary commands within affected applications.

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

As a temporary measure, you should uninstall the generator-sglk package from your project to prevent potential security breaches.

The vulnerability was identified by Amazon Inspector, a security tool that helps detect and manage vulnerabilities in software packages.

How To Fix

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

npm uninstall generator-sglk

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