# MAL-2026-16161: Malicious code in meraz-project-tracker (npm)


- **Type:** Malicious package
- **Package:** `meraz-project-tracker` (npm)
- **Published:** 14 Sep 2026
- **Also known as:** GHSA-54v8-j59m-366h

## What is MAL-2026-16161?

MAL-2026-16161 is a malicious package in meraz-project-tracker, published on 14 Sep 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-16161?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-16161 is a malicious package: meraz-project-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-16161/ (Markdown: https://insights.sbomify.com/MAL-2026-16161/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-16161

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-16161/
Summaries are generated and may contain mistakes; the official description above is the record.