NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

list-issue-predecessor-dependencies-blocknpm

Advisory published Updated

list-issue-predecessor-dependencies-block is a confirmed malicious npm package (MAL-2026-11430) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in list-issue-predecessor-dependencies-block (npm)

MAL-2026-11430
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall list-issue-predecessor-dependencies-block

What this malware does

npm package [email protected] 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.

Malicious versions

1 flagged
99.0.0

Indicators of compromise (SHA-256)

0f74d699bfc5fcf83c6f2864f93ecd41d3d9f8613f45f6bfb3b6dd5eeb7a880e
bbd4d4e3aa51ec1a7ebc0a0d4f728698503432546f139f67998849f8fff9b614

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for list-issue-predecessor-dependencies-block (version 99.0.0).

  2. If you installed it — respond

    list-issue-predecessor-dependencies-block is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If list-issue-predecessor-dependencies-block 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. list-issue-predecessor-dependencies-block on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011095

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks list-issue-predecessor-dependencies-block-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
list-issue-predecessor-dependencies-block (npm) malicious package — MAL-2026-11430 | O3 Security