Which versions of tracking-service-config are malicious?

The following npm versions of tracking-service-config are flagged malicious: 90.0.0. Treat any of these as compromised.

How do I remediate tracking-service-config if I installed it?

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

If tracking-service-config 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.

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

Search your lockfiles and build artifacts for tracking-service-config (version 90.0.0).

Malicious package

tracking-service-confignpm

Advisory published Mar 14, 2026Updated Mar 23, 2026

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

Malicious code in tracking-service-config (npm)

MAL-2026-1457

Immediate action

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

npm uninstall tracking-service-config

What this malware does

The package tracking-service-config was found to contain malicious code.

The OpenSSF Package Analysis project identified 'tracking-service-config' @ 90.0.0 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

90.0.0

Indicators of compromise (SHA-256)

be1602430f3e2d7a8afacea889ca8718d1195af57a3ad49bd4671bea7208d007

dbea868891563a569959fb4cb0283257c07da112b0e854b53431157e0a12af57

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks tracking-service-config-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