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-confusionWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package87710ad8…3b2f772b
87710ad8ef43…ee593b2f772b1 file · 1.5 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-dependency-confusion@ee0e0c5
On this page
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
- 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. - Confirm the name is unclaimed on the public registry (npm/PyPI/etc.).
- 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.
- Wait for the callback from their build/CI environment → confirms confusion.
- Scoped packages:
@company/pkgon 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,
--registrypinning, 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
- SKILL.md2.6 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
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.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 87710ad8 | Signed | – |
More from NoorQureshi
All from this publisherMore in Web and bug bounty
See the category- src-hunterzhaoxuya520/src-hunter5
- owasp-top10-analysissecurityskills/owasp-top10-analysis5
- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- offensive-xsssnailsploit/offensive-xss5
- offensive-rcesnailsploit/offensive-rce5
- source-review-techniqueaeondave/source-review-technique5
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login