Which versions of metricflow-tracker are malicious?

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

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

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

If metricflow-tracker was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is metricflow-tracker part of a known attack campaign?

Yes — metricflow-tracker is associated with the IN-MAL-2026-004911 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 metricflow-tracker across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for metricflow-tracker (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging metricflow-tracker across your stack and pipelines.

Malicious package

metricflow-trackernpm

Malicious code in metricflow-tracker (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4805

Immediate action

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

npm uninstall metricflow-tracker

What this malware does

The package's exported Metricflow React component defaults serverUrl to http://51.38.65.105:21531 and, when rendered, appends a <script src="${serverUrl}/TrakLab-plugin/Dev/tracklab.js"> tag to document.head in the consumer's web application (dist/index.js line 18). The fetched JavaScript executes with full DOM and same-origin access in any site that uses the component. The source is a bare IPv4 address over cleartext HTTP at a mutable /Dev/ path with no Subresource Integrity, no version pinning, and no TLS — whoever controls that IP, and any on-path network attacker, can serve arbitrary JavaScript into the consumer's application. Additionally, window.MetricflowConfig.collectUrl defaults to http://51.38.65.105:21531/collect, silently relaying end-user telemetry collected by the loaded tracker to the same hardcoded host. Package metadata provides no author, homepage, or documentation tying that IP to a legitimate analytics vendor. The combination of remote-code-loading from an unverified mutable HTTP endpoint plus silent relay of end-user data to an opaque destination is supply-chain harm to any installer that renders this component.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a9a1c269ce5e462d7e555ce1ca34b7f2e54e3d34ea094d35a67aa7c61d1fe34e

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for metricflow-tracker (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging metricflow-tracker across your stack and pipelines.
If you installed it — respond
Remove metricflow-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 metricflow-tracker was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks metricflow-tracker before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-004911

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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