Malicious Code Detected in build-system Package (npm)

build-system Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16324: Malicious code in build-system (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 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 build-system package is a tool designed for automating the build process in software development. It streamlines tasks such as compiling code, running tests, and packaging applications. However, this package has been identified to contain malicious code, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the build-system package. This code can potentially compromise the integrity of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and has been flagged as a critical security concern.

How To Fix

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

npm uninstall build-system

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, consider removing the build-system package from your project until a secure version is available. You can do this by executing the following command: npm uninstall build-system.

Conclusion

The build-system package has been identified to contain malicious code, posing serious security risks. Users are advised to update to a patched version or remove the package from their projects to mitigate potential threats. Monitoring tools like Vulert can help keep your applications secure.

See every vulnerability recorded for build-system →

Share this vulnerability

FAQ

The build-system package is a tool used in software development to automate the build process, including tasks like compiling code and running tests.

The malicious code was introduced in version 0 of the build-system package, which has been flagged as a security risk.

Using the compromised build-system package can lead to unauthorized access, data breaches, and other malicious activities affecting your application.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application for this vulnerability using the Vulert playground without any signup.

If you are affected, immediately update the build-system package to a patched version or remove it from your project until a secure version is available.

How To Fix

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

npm uninstall build-system

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