# MAL-2026-6196: Malicious code in build-tracker-n5p1 (npm)


- **Type:** Malicious package
- **Package:** `build-tracker-n5p1` (npm)
- **Published:** 19 Jun 2026
- **Also known as:** GHSA-chqj-php6-8x6m

## What is MAL-2026-6196?

MAL-2026-6196 is a malicious package in build-tracker-n5p1, published on 19 Jun 2026. 

### Official description

Package name suggests build telemetry tooling, but the tarball ships beacon scripts (beacon18.js, beacon_linux.js) wired to a postinstall lifecycle hook ("postinstall": "node run.js" in package.json line 9). On install, these scripts collect host identifiers via os.hostname()/os.platform() and child_process, then issue outbound HTTP GET/POST requests via http.request from the installer's machine. This combination — auto-execute on install, host fingerprinting, and outbound HTTP exfiltration — is a classic install-time host beacon / data-exfiltration pattern. There is no legitimate build-tracking reason to fingerprint the host and beacon out at install time without consent or configuration.

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-6196?

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-6196 is a malicious package: build-tracker-n5p1 (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-6196/ (Markdown: https://insights.sbomify.com/MAL-2026-6196/index.md)
```

## Sources

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

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