# MAL-2026-11430: Malicious code in list-issue-predecessor-dependencies-block (npm)


- **Type:** Malicious package
- **Package:** `list-issue-predecessor-dependencies-block` (npm)
- **Published:** 2 Aug 2026

## What is MAL-2026-11430?

MAL-2026-11430 is a malicious package in list-issue-predecessor-dependencies-block, published on 2 Aug 2026. 

### Official description

npm package list-issue-predecessor-dependencies-block@99.0.0 auto-executes index.js from three lifecycle hooks (preinstall, install, postinstall) on npm install. The script collects installer identity and environment reconnaissance — os.hostname(), os.platform(), username, current working directory, output of shell commands (whoami, id, hostname -I via child_process), CI environment variables (GITHUB_*, GITLAB_*, JENKINS_*, etc.), AWS/GCP/Azure/Kubernetes cloud-metadata indicators, enumerated names of environment variables matching /KEY|SECRET|TOKEN|PASS|CRED|AUTH|API_|PRIVATE/i, and a boolean flag for the presence of NPM_TOKEN / NODE_AUTH_TOKEN — and exfiltrates it to the hardcoded Interactsh collaborator qtmetsrtvaujwklywbgw2wihc2lebzu0n.oast.fun via DNS lookups (dns.resolve of labeled subdomains), HTTPS POST to /depconf, and HTTP POST. The high version number (99.0.0) and generic internal-sounding package name are the standard dependency-confusion shape used to override private registry packages with a public squat.

The OpenSSF Package Analysis project identified 'list-issue-predecessor-dependencies-block' @ 99.0.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

- The package executes one or more commands associated with malicious behavior.

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

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-11430 is a malicious package: list-issue-predecessor-dependencies-block (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-11430/ (Markdown: https://insights.sbomify.com/MAL-2026-11430/index.md)
```

## Sources

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

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