Malicious Code Detected in freightsmb-frontend Package

freightsmb-frontend Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20959: Malicious code in freightsmb-frontend (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 freightsmb-frontend package is a JavaScript library used in web applications for managing freight and logistics operations. It provides functionalities such as tracking shipments, managing inventory, and facilitating communication between stakeholders. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the freightsmb-frontend package arises from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or the execution of harmful operations within the application. The malicious code was introduced in version 0 and affects all subsequent versions, making it critical for users to address this issue promptly.

How To Fix

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

npm uninstall freightsmb-frontend

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 freightsmb-frontend package from your project until a secure version is released. You can do this by running the command: 'npm uninstall freightsmb-frontend'. This will prevent the execution of any malicious code while you await a fix.

Conclusion

The freightsmb-frontend package has been identified to contain malicious code that poses significant security risks. It is crucial for users to update or remove the package to protect their applications. Utilizing tools like Vulert can help monitor for vulnerabilities in real-time.

See every vulnerability recorded for freightsmb-frontend →

Share this vulnerability

FAQ

freightsmb-frontend is a JavaScript library used for managing freight and logistics operations in web applications.

The malicious code can lead to unauthorized access and potential data breaches within applications using the 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.

Users are advised to check the package repository for any patched versions of freightsmb-frontend and update accordingly.

As a temporary measure, consider uninstalling the freightsmb-frontend package to mitigate risks 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 freightsmb-frontend

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