Malicious Code Detected in blagsite Package - Security Alert

blagsite Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15799: Malicious code in blagsite (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 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 blagsite package is an npm module designed for specific functionalities within JavaScript applications. It is utilized by developers for various purposes, but recent findings have revealed that it contains malicious code, posing significant security risks to applications that depend on it. The package's widespread use makes it a target for exploitation, emphasizing the need for vigilance among developers.

Vulnerability Detail

The vulnerability in the blagsite package stems from the inclusion of malicious code that can compromise the integrity and security of applications using it. This code may allow unauthorized access, data theft, or other harmful actions, potentially leading to severe consequences for users and developers alike. The malicious nature of this code was identified through security assessments, highlighting the importance of regular package audits.

How To Fix

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

npm uninstall blagsite

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 blagsite package from your project until a secure version is released. You can do this by executing the following command: npm uninstall blagsite. This will prevent the malicious code from executing in your application.

Conclusion

The discovery of malicious code in the blagsite package poses a serious threat to applications that utilize it. Developers are urged to take immediate action by updating or removing the package to safeguard their projects. Continuous monitoring and auditing of dependencies are essential to maintain security in software development.

See every vulnerability recorded for blagsite →

Share this vulnerability

FAQ

Blagsite is an npm package used in JavaScript applications, but it has been found to contain malicious code.

You can use Vulert to monitor and alert for open-source vulnerabilities in your application. Check your package-lock.json file with Vulert's playground at Vulert Scanner.

Immediately update the blagsite package to the latest version or remove it from your project until a secure version is available.

Using a compromised package can lead to unauthorized access, data breaches, and other security incidents that can harm both users and developers.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about security advisories related to the packages you use.

How To Fix

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

npm uninstall blagsite

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