HighAdvisory sweepnpm6 affected versions

browser-metrics-plugin.contrib

browser-metrics-plugin.contrib has 6 versions on the npm registry flagged in 1 incident we track. Only the exact versions listed below were named by the source advisories.

browser-metrics-plugin.contrib was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.

Affected versions

Check what you actually have installed with npm ls browser-metrics-plugin.contrib.

browser-metrics-plugin.contrib@99.0.1
browser-metrics-plugin.contrib@2.0.1
browser-metrics-plugin.contrib@1.1.0
browser-metrics-plugin.contrib@1.0.1
browser-metrics-plugin.contrib@1.0.0
browser-metrics-plugin.contrib@0.0.1

The incident that flagged it

High8 Oct 2026

GitHub Advisory malware sweep - 2026-10-08 (named compromise carve-out: `tensorlake@0.5.144` maintainer-account compromise; plus npm `internallib_v788` wave-3 continuation of the `internallib_v<N>` RFC1918 reverse-shell operator; new npm `troubleshooting`/`browser-metrics-plugin.contrib` dep-confusion probe from `xwise8887` with HTTP beacon to `185.158.107.175:8787`; new npm `personio-pipeline-projen` dep-confusion probe from `reaperhackbot256f` with `oast.fun`+`oastify.com` DNS/HTTPS exfil; new npm `imgbundle`+`cdn-img-fetch` img-themed sleeper cluster from `malfexteste2`; npm `function-color@1.7.3`+`function-flag@1.7.3` 2025-08-04 backfilled low-version sideload sleepers caught today; 3-package npm `@ikyyjee/ikkysingle`/`ikyysingle`/`ikyysinggle` typosquat burst; 2 Amazon-Inspector namespace-holder takedowns `windows_registry_editor`/`store-webpack-config`; and 5 CWE-506 boilerplate takedowns)

GHSA 2026-10-08: 20 fresh malware advisories across 9 clusters (19 npm, 1 pypi carried forward from end-of-day yesterday). The dominant story is the tensorlake maintainer-account compromise (tensorlake@0.5.144 published one patch above the real 0.5.143 latest of the official TensorLake AI SDK - carved out as its own named incident). Also: wave-3 of the internallib_v<N> RFC1918 reverse-shell operator (internallib_v788); two new dep-confusion probes with confirmed network beacons; a 2-package img-themed sleeper cluster; two 2025-08-04 sideload sleepers (function-color/function-flag@1.7.3) caught today; and a 3-package @ikyyjee typosquat burst.

Versions named here: 0.0.1, 1.0.0, 1.0.1, 1.1.0, 2.0.1, 99.0.1

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

browser-metrics-plugin.contrib is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once - it runs in your browser and nothing is uploaded.

Check my package-lock.json All flagged npm packages

Other packages in the same incident

If browser-metrics-plugin.contrib is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.