Which versions of adobe-tracking are malicious?

The following npm versions of adobe-tracking are flagged malicious: 100.0.0. Treat any of these as compromised.

How do I remediate adobe-tracking if I installed it?

Remove adobe-tracking from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed adobe-tracking — how do I know if it already compromised me?

If adobe-tracking was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is adobe-tracking part of a known attack campaign?

Yes — adobe-tracking is associated with the RLMA-2026-01094 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find adobe-tracking across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for adobe-tracking (version 100.0.0).

Malicious package

adobe-trackingnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

adobe-tracking is a confirmed malicious npm package (MAL-2026-1647) that executes malicious code on install (malicious version 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in adobe-tracking (npm)

MAL-2026-1647

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall adobe-tracking

What this malware does

The package adobe-tracking was found to contain malicious code.

Malicious versions

1 flagged

100.0.0

Indicators of compromise (SHA-256)

53ef1a86384f8786cf1c9e3a63f5fdf4297a3d067504c801bc3ae2e16742dded

9ea7322d0f5d2ca7aa6671313fe1f8f467c5db667987215e36535698aa5885df

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for adobe-tracking (version 100.0.0).
If you installed it — respond
Remove adobe-tracking from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If adobe-tracking was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. adobe-tracking on npm has been identified as a malicious package (version 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01094

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks adobe-tracking-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database