Irritatingly, this doesn't turn up anything, despite having a theoretically-compromised project as per the package-lock.json… At least on my end

▲

mewpmewp2 4 days ago | parent | next [-]

What do you mean irritatingly? Do you mean that you think 'grep -r "_0x112fa8"' is not enough or are you irritated that npm audit is flagging as if it was compromised?

	▲	9dev 4 days ago \| parent [-]
		I'm irritated because I expected to find at least one compromised file, but there were none. It may be, though, that we only use the affected packages as transitive development dependencies, in which case they are not installed locally. But a sliver of doubt remains that I missed something.

▲

AgentME 4 days ago | parent | prev [-]

If you had the dependency installed before this attack, then you would still be pinned to an old safe version.