Malicious Code Detected in gohelix Package - Security Alert

gohelix Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21632: Malicious code in gohelix (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 gohelix package is an npm library designed for managing and orchestrating workflows in a streamlined manner. It is commonly used in various applications to enhance automation and efficiency. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the gohelix package stems from the inclusion of malicious code that can compromise the integrity and security of applications utilizing this library. This code may allow unauthorized access, data exfiltration, or other harmful actions, potentially leading to severe consequences for affected systems. The malicious code was introduced in version 0 and has been confirmed by security researchers.

How To Fix

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

npm uninstall gohelix

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 workaround, you may consider removing the gohelix package from your project until a secure version is released. You can do this by executing the following command: npm uninstall gohelix. This will help mitigate the risk while you await a fix.

Conclusion

The gohelix package has been identified to contain malicious code, posing serious security risks to applications that utilize it. Users are advised to update the package to a secure version or remove it until a fix is available. Continuous monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for gohelix →

Share this vulnerability

FAQ

The gohelix package is used for managing and orchestrating workflows in applications, enhancing automation and efficiency.

The malicious code was discovered by security researchers from Amazon Inspector, who identified the vulnerabilities in the package.

Using the compromised gohelix package can lead to unauthorized access, data breaches, and potential exploitation of your application.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.

If you cannot update the package immediately, consider removing it from your project as a temporary measure to mitigate risks.

How To Fix

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

npm uninstall gohelix

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