Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

meraz-project-trackernpm

Advisory published Updated

meraz-project-tracker is a confirmed malicious npm package (MAL-2026-16161) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in meraz-project-tracker (npm)

MAL-2026-16161
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall meraz-project-tracker

What this malware does

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.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

e1a3c77d5bcaa115429f3dd8340c5ab055c399f7d240842ea8f57b60bcb8f4f2
d3081e87039a0a1582330f353797d15ba12cdb1c17828ab2ee7224b7c1ac4809

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for meraz-project-tracker (version 1.0.0).

  2. If you installed it — respond

    Remove meraz-project-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.

  3. Did it already run?

    If meraz-project-tracker was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. meraz-project-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

GHSA-54v8-j59m-366hIN-MAL-2026-020070

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks meraz-project-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.

Explore

meraz-project-tracker (npm) malicious package — MAL-2026-16161 | O3 Security