|
|
|
|
|
by afishhh
242 days ago
|
|
Using non-printable characters to encode malicious code is creative, but I wouldn't say it "breaks our security model". I would be pretty suspicious if I saw a large string of non-printable text wrapped in a decode() function during code review... Hard to find a legitimate use for encoding things like this. Also another commenter[1] said there's an eval of the decoded string further down the file, and that's definitely not invisible. Has no one thought to review the AI slop before publishing? [1] https://news.ycombinator.com/item?id=45649224 |
|
> Has no one thought to review the AI slop before publishing?
If only Koi reviewed their AI slop before publishing :(