Malicious Code Detected in dynseg-util: A Critical Security Alert

dynseg-util Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19039: Malicious code in dynseg-util (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 dynseg-util package is an npm library designed for utility functions related to dynamic segmentation. It is commonly used in various JavaScript applications for its ease of integration and functionality. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in dynseg-util stems from the inclusion of malicious code within the package. This code can potentially compromise the security of applications that depend on it, leading to unauthorized access, data breaches, or other malicious activities. The issue was first identified in version 0 and affects all subsequent versions, making it critical for developers to address this vulnerability promptly.

How To Fix

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

npm uninstall dynseg-util

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 dynseg-util package from your project until a secure version is released. You can do this by executing: npm uninstall dynseg-util. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The discovery of malicious code in the dynseg-util package highlights the importance of regularly monitoring and updating dependencies in software projects. Developers should take immediate action to secure their applications by updating or removing the affected package.

See every vulnerability recorded for dynseg-util →

Share this vulnerability

FAQ

dynseg-util is an npm package that provides utility functions for dynamic segmentation in JavaScript applications.

The malicious code found in dynseg-util can lead to unauthorized access and potential data breaches in applications that use this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

As of now, it is crucial to check the package repository for any updates or patches that address the malicious code issue.

If you cannot update dynseg-util immediately, consider removing it from your project as a temporary measure to avoid exposure to the vulnerability.

How To Fix

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

npm uninstall dynseg-util

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