Critical Malicious Code Vulnerability in scgsffcreator Package

scgsffcreator Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190781: Malicious code in scgsffcreator (npm). Affects scgsffcreator versions 1.0.5. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The scgsffcreator package is an npm library designed for creating and managing SCGSFF files. It is utilized in various applications for its ease of use and functionality. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and organizations relying on it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the scgsffcreator package, specifically version 1.0.5. This code can lead to full compromise of the system, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to malicious actors who have intentionally inserted harmful code into the package, which can execute harmful actions once the package is installed. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall scgsffcreator

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 are no effective workarounds for this vulnerability other than removing the package entirely. Users should ensure that they do not use any functionality provided by scgsffcreator until the package is confirmed to be safe.

Conclusion

The scgsffcreator package has been identified as containing malicious code that poses a serious security risk. Immediate action is required to remove the package and secure any sensitive information. Users should remain vigilant and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for scgsffcreator →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on the affected system.

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.

No, there is currently no patched version available for the scgsffcreator package. The only solution is to remove it.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and full system compromise.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure to review package sources and maintain updated security practices.

How To Fix

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

npm uninstall scgsffcreator

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