Malicious Code Detected in sbrugna Package - Security Alert

sbrugna Updated 02 Oct 2025

Summary

16/09/2025
CRITICAL
No i
Critical
Not published

MAL-2025-47409: Malicious code in sbrugna (npm). Affects sbrugna versions >= 1.0.1. 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 sbrugna package is an npm library designed for specific functionalities within JavaScript applications. It is commonly used for various tasks, but its recent vulnerability has raised concerns about its security. The package has been found to communicate with a domain linked to malicious activities, posing risks to users and their applications.

Vulnerability Detail

The vulnerability in the sbrugna package originates from its communication with a domain associated with malicious activities. This can lead to unauthorized data access, potential data breaches, and exploitation of the affected systems. The malicious code can compromise the integrity of applications using this package, making it crucial for developers to address this issue promptly.

How To Fix

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

npm uninstall sbrugna

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 measure, you can remove the sbrugna package from your project until a secure version is released. To uninstall the package, run the following command: npm uninstall sbrugna. This will prevent any potential malicious activity while you seek a safer alternative.

Conclusion

The sbrugna package has been identified as having a significant vulnerability due to its communication with a malicious domain. It is essential for developers to update the package to the latest version or remove it entirely until a secure version is available. Monitoring tools like Vulert can assist in keeping your applications safe from such vulnerabilities.

See every vulnerability recorded for sbrugna →

Share this vulnerability

FAQ

sbrugna is an npm package used in JavaScript applications for various functionalities. However, it has recently been flagged for security vulnerabilities.

The vulnerability allows the package to communicate with a malicious domain, which can lead to unauthorized access to your application's data and potential exploitation.

Yes, users are encouraged to update to the latest version of the sbrugna package to mitigate the risks associated with this vulnerability.

You can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file. Visit https://vulert.com for more information.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall sbrugna

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