Supply-chain attack using invisible code hits GitHub and other repositories
arstechnica.comWeird article. The author talks about Unicode "public use areas" (which don't exist), clarifies that they're sometimes called "public use access" (a term appearing only in this article) and are invisible while also being used for flags and emojis and also having special meaning to JavaScript interpreters and also representing letters in the "US alphabet".
There's a real vulnerability here but whoever wrote this has no idea what they're talking about.
Can anyone recommend any OSS tooling that could be used in something like a GH action workflow to automatically screen for these types of static attacks on code? Seems like something that should be part of an automated review pipeline if it's getting so hard for humans to visually review against this kind of stuff.
A linter that disallows any code that uses eval in any form seems like a good start to me.
What about for languages that allow pretty much anything in identifiers or variables. JS for example. Or bash. Don't need eval to do anything crazy there.