Gate News message. On March 31, the SlowMist security team issued an alert. As of March 31, 2026, public intelligence shows that axios@1.14.1 and axios@0.30.4 have both been confirmed as malicious versions. Both have been implanted with an additional dependency, plain-crypto-js@4.2.1. This dependency can deliver cross-platform malicious payloads via a postinstall script.
The impact of this incident on OpenClaw needs to be judged by scenario: 1) In the source build scenario, there is no impact. In v2026.3.28, the lock file actually locks axios@1.13.5 / 1.13.6, which does not match the malicious versions; 2) In the scenario of running npm install -g openclaw@2026.3.28, there is a risk of historical exposure. The reason is that the dependency chain includes openclaw -> @line/bot-sdk@10.6.0 -> optionalDependencies.axios@^1.7.4. Within the time window when the malicious versions are still online, it may resolve to axios@1.14.1; 3) The current reinstallation results show that npm has rolled back resolution to axios@1.14.0. However, for environments where installation occurred within the attack window, it is still recommended to treat it as an affected scenario and investigate IoC.
SlowMist advises that if a plain-crypto-js directory is found, even if its package.json has been cleaned up, it should be treated as a high-risk execution artifact. For hosts that ran npm install or npm install -g openclaw@2026.3.28 within the attack window, it is recommended to immediately rotate credentials and conduct host-side investigation.