Which versions of latency-tracking are malicious?

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

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

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

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

Yes — latency-tracking is associated with the RLMA-2026-05137, RLUA-2026-06300 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 latency-tracking across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for latency-tracking (version 99.9.0).

Malicious package

latency-trackingnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in latency-tracking (npm)

MAL-2026-7309

Immediate action

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

npm uninstall latency-tracking

Malicious versions

1 flagged

99.9.0

Indicators of compromise (SHA-256)

8c5ee150b741014108153a144d600f22abb631438c5b2b559e66cd362f214ff6

51279ea708e8c3fb9ede4c62c21f49b73746c85e63e023a522fc242d5afff795

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05137RLUA-2026-06300

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks latency-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