Sink boundary: Input controls object keys that can modify shared prototype state.
The pack does not provide a callable signature for this record; the watched access path is shown directly.
| Arg | Access path | Purpose | Watched |
|---|---|---|---|
| Argument[0] | Argument[0] | The access path Atropos marks for this model. | ▲ sink |
Attacker's-eye view · prototype-pollution
A crafted key such as a prototype path changes defaults or behavior for unrelated objects.
// modeled boundary: Argument[0]
computed-property-write(attacker_influenced_value);
1Reject prototype keys.
2Use own-property checks and safe merge APIs.
3Keep parsed data in null-prototype objects where appropriate.
These checks require the surrounding codebase. The model names the boundary; it does not decide reachability or prove that a guard dominates every path.
Is this a bug in your code?Atropos stops here — by design
Atropos identifies Argument[0] as a prototype-pollution sink. It cannot see whether untrusted data reaches this call in your repository.
Lachesis is the codebase-level step: it traces reachability and guards for this symbol.
Check this symbol in Lachesis →Same behavior
●defaultsDeepjavascript●mergejavascript●mergeWithjavascript●setjavascript●setWithjavascript●plainToClasstypescriptAcross languages
●plainToClasstypescript●plainToInstancetypescript●defaultsDeeptypescript●mergetypescript●mergeWithtypescript●settypescriptWhat neutralizes it
No sanitizer of this kind is modeled.
Model facts · verbatim from the pack
| Role | Kind | Access path | Model ID | Confidence |
|---|---|---|---|---|
| sink | prototype-pollution | Argument[0] | javascript.proto.computed-write.a0 | low · corrob. 1 |