What is prototype pollution and why does it matter in Node?
PICTURE THIS: GIT FLOW
Simple meaning
Prototype pollution writes to Object.prototype through unsanitized merge of user JSON.
WHY — Security instead of guessing?
Why interviewers care about Security:
who only read docs from people who shipped.
and tied to Full Stack work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Prototype pollution writes to
Object.prototype through unsanitized merge of user JSON.
- 2Later code then inherits
attacker-controlled properties such as isAdmin.
- 3Avoid recursive merges of
req.body and keep prototype-safe parsers.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Prototype pollution writes to Object.prototype through unsanitized merge of user JSON. Later code then inherits attacker-controlled properties such as isAdmin.