MAL-2026-4805 Malicious code in metricflow-tracker (npm)
Malicious package
Published
MAL-2026-4805 is a malicious package: metricflow-tracker (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-4805/ (Markdown: https://insights.sbomify.com/MAL-2026-4805/index.md)
- Package
- metricflow-tracker
- Registry
- npm
What is MAL-2026-4805?
MAL-2026-4805 is a malicious package in metricflow-tracker, published on 26 May 2026.
Official description
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.What should I do about MAL-2026-4805?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.