Malicious Code Detected in decawave Package - Security Alert

decawave Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18148: Malicious code in decawave (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The decawave package is an npm library designed for specific functionalities related to Decawave technology, which is often used in applications requiring precise location tracking and communication. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the decawave package stems from the inclusion of malicious code that can compromise the integrity and security of applications utilizing this package. This issue was introduced in version 0 and affects all subsequent versions. The ramifications of this vulnerability include potential data breaches, unauthorized access to sensitive information, and the possibility of the package being used as a vector for further attacks.

How To Fix

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

npm uninstall decawave

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

Conclusion

The discovery of malicious code in the decawave package highlights the importance of regularly monitoring and updating open-source dependencies. Users are strongly encouraged to take immediate action by updating or removing the package to safeguard their applications.

See every vulnerability recorded for decawave →

Share this vulnerability

FAQ

The decawave package is utilized for functionalities related to Decawave technology, primarily in applications requiring precise location tracking.

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.

If an immediate update is not possible, consider removing the package from your project as a temporary workaround until a secure version is available.

Using the compromised decawave package can lead to data breaches, unauthorized access, and potential exploitation of your application.

Detailed information about the vulnerability can be found in the Open Source Vulnerability database and on the GitHub repository for malicious packages.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall decawave

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