Attackers took over the account of a maintainer of Axios, one of the most widely used JavaScript packages, and published two poisoned releases. Versions 1.14.1 and 0.30.4 were available for roughly three hours before being removed. Google attributed the attack to UNC1069, a group it links to North Korea.
What is going on
The attackers did not break any code. They posed as a company, contacted the maintainer on LinkedIn and Slack, and set up a Microsoft Teams call.
During the call they showed him a fake error message and offered a fix. The "fix" was remote access malware, known as a RAT, which gives an attacker control of the computer. With that access they published new Axios versions containing a malicious dependency called plain-crypto-js.
Think of it as a courier in a convincing uniform talking a warehouse manager into handing over his keys. Nothing was forced open; the trust was.
Who is affected
Only installs of Axios 1.14.1 or 0.30.4 during that short window are a concern. That includes any JavaScript project, website build or server that pulled in a fresh copy of Axios while those versions were live.
Most small business sites install packages rarely, so the risk is limited. The bigger risk sits with developers and agencies who run builds daily, and with automated pipelines that fetch the newest version each time.
What to do now
- Ask your developer or agency whether any build installed Axios 1.14.1 or 0.30.4, and when.
- If either version was installed, treat that machine or server as compromised and have it rebuilt rather than cleaned.
- Rotate all credentials that the affected system could reach: hosting logins, API keys, database passwords, deployment tokens.
- Pin your dependencies with a lockfile so builds install a fixed, reviewed version instead of whatever is newest.
- Remind your team that software updates offered during a call or chat are never installed on the spot, no matter how convincing the caller is.
How to check your own site
A scan cannot see inside your build pipeline, but it can show what your site exposes to the outside world afterwards. The free Website Security Check flags outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If you want deeper coverage after an incident, you can run a full scan for exposed files, leaked secrets and service checks with CVE matching, on sites whose ownership you have verified.
Source: BleepingComputer, December 2025.
Comments
No comments yet.