The big npm incident from last week was the Axios compromise on March 31, 2026. The malicious releases were axios@1.14.1 and axios@0.30.4, and they pulled in a trojanized dependency, plain-crypto-js@4.2.1, which ran a postinstall hook and fetched a cross-platform RAT from sfrclak[.]com:8000. The bad versions were live for roughly 00:21–03:29 UTC on March 31, so in Greece that was about 03:21–06:29 on March 31. If your machine or CI ran a fresh install in that window and resolved one of those versions, you should treat it seriously. ([Google Cloud][1])
What matters most is this: if your lockfile or install artifacts show axios@1.14.1, axios@0.30.4, or plain-crypto-js, the Axios maintainer’s own postmortem says to treat that machine as compromised, rotate every secret on it, and check for outbound traffic to sfrclak[.]com or 142.11.206.73 on port 8000. If you were pinned to a clean version and did not do a fresh install during the bad window, you are probably fine. ([GitHub][2])
Use this t