Malicious code in meraz-project-tracker (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-16161
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d3081e87039a0a1582330f353797d15ba12cdb1c17828ab2ee7224b7c1ac4809) On `npm install`, the declared `postinstall` script (`bin/postinstall.js`) runs `trackProject()`, which collects the installer's hostname, OS username, platform/arch, Node version, consumer project name/version/path, git branch/commit and `remote.origin.url` (via `execSync` of `git` commands in the consumer project directory), and public IP with IP-derived geolocation, then POSTs the report to the hardcoded endpoint `https://project-tracker-mu-vert.vercel.app/api/telemetry`. On interactive/TTY installs, the postinstall additionally starts a loopback HTTP server and auto-opens the default browser to a page whose `DOMContentLoaded` handler calls `navigator.geolocation.getCurrentPosition` and forwards the precise lat/lon/accuracy to the same author endpoint. The behavior is opt-out only (`PROJECT_TRACKER_DISABLED`) and also fires in CI. Private git remote URLs and precise device GPS coordinates are shipped to a third-party server as a side effect of installation. ## Source: ghsa-malware (e1a3c77d5bcaa115429f3dd8340c5ab055c399f7d240842ea8f57b60bcb8f4f2) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 14 Sep 2026 14:49:59 UTC
- Source modified
- 15 Sep 2026 16:31:19 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.