Malicious Code Vulnerability in adobe-tracking Package

adobe-tracking Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1647: Malicious code in adobe-tracking (npm). Affects adobe-tracking versions 100.0.0. 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 adobe-tracking package is an npm library designed for tracking user interactions and analytics within Adobe applications. It provides developers with tools to integrate Adobe's tracking capabilities seamlessly into their web applications. However, this package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within version 100.0.0 of the adobe-tracking package. This code can potentially compromise the integrity of applications that depend on this package, leading to unauthorized access, data breaches, or other malicious activities. The origin of this vulnerability is linked to the package's distribution through npm, where it was identified and reported by ReversingLabs.

How To Fix

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

npm uninstall adobe-tracking

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, you can remove the adobe-tracking package from your project until a secure version is released. You can do this by executing the following command: npm uninstall adobe-tracking. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The adobe-tracking package has been identified as containing malicious code, posing significant risks to applications that utilize it. It is crucial to update or remove the package to mitigate these risks. Regular monitoring of dependencies using tools like Vulert can help maintain application security.

See every vulnerability recorded for adobe-tracking →

Share this vulnerability

FAQ

The adobe-tracking package is used for integrating Adobe's tracking capabilities into web applications, allowing developers to monitor user interactions and analytics.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If you cannot update the package immediately, consider removing it from your project and using alternative packages until a secure version is available.

The vulnerability was reported by ReversingLabs, a security research firm that specializes in identifying malicious packages.

Using the compromised version of adobe-tracking can lead to unauthorized access, data breaches, and other malicious activities that can compromise your application's security.

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 adobe-tracking

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