Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/web-dependency-confusionWeb and bug bounty

web-dependency-confusion

⁨Dependency confusion / substitution — publish a malicious public package matching an internal name so build systems pull yours. Load on leaked internal package names (npm/PyPI/RubyGems/Maven), package.json/requirements with unknown deps, or private-registry setups. Signals: @scope/internal packages,⁩

v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/web-dependency-confusion

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
jtV9DrYyvL…m7Z2F7AA==The CLI checks the SHA-256 and the signature before it writes a file.
Package87710ad8…3b2f772b
87710ad8ef43…ee593b2f772b1 file · ⁦1.5 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-dependency-confusion@ee0e0c5

When it applies

The target builds software using internal package names that aren't published publicly, on an ecosystem (npm, PyPI, RubyGems, Maven, NuGet) where a public registry is also consulted. If you can learn an internal name and publish it publicly, their resolver may fetch your package → RCE in their build/CI.

Why it works

Many package managers, misconfigured, prefer the highest version across all configured registries — public included. Publishing [email protected] to the public registry can outrank the private [email protected], so builds pull and execute your code (install scripts run automatically).

Method

  1. Harvest internal names: leaked package.json/requirements.txt/pom.xml, source maps and JS bundles (→ recon-js-analysis), error messages, public repos, .npmrc/registry config.
  2. Confirm the name is unclaimed on the public registry (npm/PyPI/etc.).
  3. Publish a benign PoC package under that exact name with a high version, whose install/postinstall step makes an OOB callback (DNS/HTTP to your collaborator) including hostname/user — no destructive payload. This proves execution if their build pulls it.
  4. Wait for the callback from their build/CI environment → confirms confusion.
  5. Scoped packages: @company/pkg on npm needs the scope unclaimed; note the config that would prevent it.

Gotchas

  • Keep the payload benign and identifiable (your marker only) — you're proving exec, not attacking. Mind program RoE (many bug-bounty programs have specific rules for this).
  • Proper configs (scoped registries, --registry pinning, namespace ownership) prevent it — the finding is the missing control.
  • Take down the package after reporting.

Verify success

An OOB callback from the target's build/CI proving your public package was resolved and its code executed.

References

Alex Birsan "Dependency Confusion"; npm/PyPI scoping & registry-pinning docs.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c587710ad8Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login