Malicious Code Injection in siriusbeyond Package

siriusbeyond Updated 21 Sep 2026

Summary

21/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16343: Malicious code in siriusbeyond (npm). Affects siriusbeyond versions 1.0.0. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The siriusbeyond package is an npm library designed for various functionalities within JavaScript applications. However, it has been found to contain malicious code that executes during the installation process, posing significant security risks to users and their environments.

Vulnerability Detail

The vulnerability stems from the inclusion of a malicious script (callback.js) that is triggered during both the preinstall and postinstall lifecycle hooks of the npm package. When a user runs 'npm install siriusbeyond', this script collects sensitive information such as hostname, username, and various environment variables that resemble credentials. This data is then sent to a remote server via a hardcoded Telegram bot token, potentially leading to credential theft and further exploitation. The script also attempts to exfiltrate data through DNS tunneling if outbound HTTPS is blocked.

How To Fix

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

npm uninstall siriusbeyond

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, avoid using the siriusbeyond package in your projects. If it is already installed, you can remove it with the command: 'npm uninstall siriusbeyond'. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The siriusbeyond package poses a serious security threat due to the presence of malicious code that collects sensitive information. Users are advised to remove the package and monitor their applications for any vulnerabilities using tools like Vulert.

See every vulnerability recorded for siriusbeyond →

Share this vulnerability

FAQ

The package contains malicious code that collects sensitive information during installation and sends it to a remote server.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

You should uninstall the package immediately using 'npm uninstall siriusbeyond' and monitor your environment for any suspicious activity.

As of now, there is no patched version available. It is advisable to remove the package until a safe version is released.

Vulert uses your package-lock.json file to monitor and alert you in real-time for any open-source vulnerabilities in your software.

How To Fix

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

npm uninstall siriusbeyond

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