Checking If a Javascript Native Function Is Monkey Patched (2022)
Posted4 months agoActive4 months ago
mmazzarolo.comTechstory
controversialmixed
Debate
80/100
JavascriptSecurityDrm
Key topics
Javascript
Security
Drm
The article discusses ways to detect if a JavaScript native function has been monkey patched, sparking a debate about the motivations and implications of such detection.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
3d
Peak period
3
84-90h
Avg / period
2
Key moments
- 01Story posted
Sep 8, 2025 at 2:57 PM EDT
4 months ago
Step 01 - 02First comment
Sep 11, 2025 at 9:16 PM EDT
3d after posting
Step 02 - 03Peak activity
3 comments in 84-90h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 12, 2025 at 6:44 PM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45172330Type: storyLast synced: 11/20/2025, 7:50:26 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
"malicious" according to who? Somehow this article makes me think those trying to do things like this are on the pro-DRM side, which I absolutely abhor. The slow and forceful insertion of JS where it's not needed means users will increasingly need to inject and modify JS to retain control of their experience.
https://www.aikido.dev/blog/npm-debug-and-chalk-packages-com...
Considering there's no way to check whether a function is monkey-patched, this just tells me the JavaScript ecosystem was not designed with malicious actors in mind
joke is on you, adblock loads first and there is no way you will grab unmodified functions to detect it