skool-monitor

SUSPICIOUS: The core read/write capability matches the stated purpose, but the auth and execution model is weaker than expected. The main concerns are use of a reverse-engineered API, browser-cookie/session-token handling that conflicts with Skool's own security guidance, and automation of account actions on a platform that discourages bots. No evidence shows overt malware, remote payload delivery, or third-party credential exfiltration.

The code implements an authenticated comment scraper and shows no clear malicious behavior or data exfiltration beyond its intended Skool API access. Direct interpolation of post IDs and API cursors into evaluated JavaScript is a meaningful injection risk when those values are untrusted. Use safe JavaScript argument passing and validate or encode URL components.