Malicious Code Detected in active_shipping Package - MAL-2025-14044

active_shipping Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14044: Malicious code in active_shipping (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The active_shipping package is a widely used library in the npm ecosystem that facilitates shipping and logistics operations within applications. It provides functionalities such as calculating shipping rates, generating shipping labels, and tracking shipments. However, the package has been found to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the active_shipping package arises from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue originates from version 0 of the package and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall active_shipping

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, users may consider removing the active_shipping package from their project until a secure version is released. This can be done using the command: 'npm uninstall active_shipping'. Alternatively, users can explore other shipping libraries that do not have this vulnerability.

Conclusion

The discovery of malicious code in the active_shipping package highlights the importance of maintaining secure dependencies in software projects. Users are urged to take immediate action to update or remove the affected package to safeguard their applications.

See every vulnerability recorded for active_shipping →

Share this vulnerability

FAQ

active_shipping is an npm package that provides functionalities for shipping and logistics operations in applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using the package.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you cannot update the package right away, consider uninstalling it or using alternative libraries until a secure version is available.

Monitor the package repository on npm or GitHub for announcements regarding updates and patches related to this vulnerability.

How To Fix

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

npm uninstall active_shipping

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