Critical Malicious Code Vulnerability in nebula-sdk Package

nebula-sdk Updated 28 Sep 2026

Summary

28/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17219: Malicious code in nebula-sdk (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 nebula-sdk package is a Node.js library designed for developers to facilitate interactions with the Nebula platform. It provides various functionalities, including API access and data manipulation. However, this package has been identified as containing malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the nebula-sdk package. This code can compromise the entire system where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it can lead to complete control of the affected machine by external entities. Users are advised to treat any system running this package as fully compromised.

How To Fix

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

npm uninstall nebula-sdk

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 workaround, it is recommended to rotate all secrets and keys stored on the affected computer from a different, secure machine. This action helps mitigate the risk of unauthorized access resulting from the malicious code.

Conclusion

The nebula-sdk package has been identified as containing malicious code, posing a significant security risk to any system using it. Immediate action is required to remove the package and secure sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for nebula-sdk →

Share this vulnerability

FAQ

Immediately remove the nebula-sdk package and rotate any sensitive information stored on the affected machine.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Failure to address this vulnerability can lead to unauthorized access to sensitive data and complete control of your system by malicious actors.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json, allowing you to stay informed about potential risks.

How To Fix

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

npm uninstall nebula-sdk

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