Which versions of declarative-tracker are malicious?

The following npm versions of declarative-tracker are flagged malicious: 9999.0.0. Treat any of these as compromised.

How do I remediate declarative-tracker if I installed it?

Remove declarative-tracker 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 declarative-tracker — how do I know if it already compromised me?

If declarative-tracker 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 declarative-tracker part of a known attack campaign?

Yes — declarative-tracker is associated with the RLMA-2026-01933 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 declarative-tracker across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for declarative-tracker (version 9999.0.0).

Malicious package

declarative-trackernpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

declarative-tracker is a confirmed malicious npm package (MAL-2026-2753) that executes malicious code on install (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in declarative-tracker (npm)

MAL-2026-2753

Immediate action

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

npm uninstall declarative-tracker

What this malware does

The package declarative-tracker was found to contain malicious code.

Malicious versions

1 flagged

9999.0.0

Indicators of compromise (SHA-256)

d4a65f59b6839f4f613664aa8a18cfed7ec6c4f8c5fa34ba5f4d8f7af5edab59

89088e7f5550589f29e7d93c3456772ccbab6a6cb324f69184bb12101420256a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for declarative-tracker (version 9999.0.0).
If you installed it — respond
Remove declarative-tracker 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 declarative-tracker 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. declarative-tracker on npm has been identified as a malicious package (version 9999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01933

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks declarative-tracker-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