Malicious Code Detected in @siriusbeyond/auth Package: Security Risk Alert

@siriusbeyond/auth Updated 21 Sep 2026

Summary

20/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16320: Malicious code in @siriusbeyond/auth (npm). Affects @siriusbeyond/auth versions 99.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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The @siriusbeyond/auth package is an npm library that is intended for authentication purposes. However, version 99.0.0 of this package has been identified as malicious, embedding harmful code that compromises user data. The package registers preinstall and postinstall lifecycle scripts that execute a script named callback.js, which collects sensitive information from the user's environment.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the @siriusbeyond/auth package version 99.0.0. This code executes during the installation process, collecting sensitive data such as the hostname, username, and environment variables that may contain tokens or passwords. The collected data is then sent to a Telegram channel controlled by the attacker, posing a significant risk to user privacy and security. The package's design exploits dependency confusion, allowing it to be installed in environments that reference the @siriusbeyond scope, leading to potential data breaches.

How To Fix

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

npm uninstall @siriusbeyond/auth

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 can prevent the installation of the malicious package by using npm's package-lock.json to lock your dependencies to a safe version. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities in real-time.

Conclusion

The @siriusbeyond/auth package version 99.0.0 contains malicious code that poses a serious security risk by collecting sensitive user data. It is crucial to uninstall this version and monitor your dependencies to prevent future vulnerabilities. Utilizing tools like Vulert can help maintain the security of your open-source software.

See every vulnerability recorded for @siriusbeyond/auth →

Share this vulnerability

FAQ

The vulnerability involves malicious code that collects sensitive user data and sends it to an external Telegram channel.

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

You should uninstall the affected version and install the latest secure version of the package to mitigate the risk.

The malicious code is executed through preinstall and postinstall lifecycle scripts that run automatically when the package is installed.

Yes, regularly monitor your dependencies using tools like Vulert and ensure to review package integrity before installation.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall @siriusbeyond/auth

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