Repositório GitHub antd-img-crop · Exploitation confirmed

[Single source] Forged antd-img-crop commit installed Overlord RAT when developers ran npm run build

· 1 min read

A forged commit in the antd-img-crop GitHub repository used a malicious prebuild hook to deploy Overlord RAT when developers ran npm run build. The npm package itself was not affected, TheHackersNews reports. Teams that built the project from source should check their environments.

Illustration: Forged antd-img-crop commit installed Overlord RAT when developers ran npm run build
WhatsApp LinkedIn X
HighSupply chainExploitation confirmedFix unconfirmed

In 30 seconds

TheHackersNews
Alleged

A routine build command may have been the trigger for a malware infection. Security outlet TheHackersNews reported on X that a forged commit in the antd-img-crop GitHub repository carried a malicious prebuild hook, meaning a script that runs automatically before a build, and that this hook deployed a RAT, short for remote access trojan, a type of malware that hands an attacker remote control of a machine. According to the report, the trap sprang when developers ran npm run build, the standard command for compiling the project from source.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Alleged

The report adds one important boundary: the antd-img-crop package on npm itself was not affected. In other words, the claimed exposure path ran through source code pulled from GitHub, not through the package that most users install.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

What happened

Alleged

Here is the causal chain as the report lays it out. A forged commit was inserted into the antd-img-crop repository on GitHub. That commit included a malicious prebuild hook. When a developer ran the build command, the hook executed, and the payload it delivered is identified as Overlord RAT. The npm package, the version distributed through the registry, is said to have stayed clean.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Inferred

The word forged suggests the repository's code history was tampered with rather than the published package being replaced, though the post does not explain how the commit got there, who put it there, or when it landed.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Why it matters

Inferred

Build hooks are a nasty infection vector because they weaponize trust. A developer types a familiar command, and the toolchain silently executes attacker code with that developer's own permissions before any compilation output ever appears. Nothing looks unusual until it is too late.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Inferred

The split between a poisoned repository and a clean npm package matters for scoping. Teams that build from source, whether locally or in CI pipelines, sat on the exposure path described in the report, while the much larger population that simply installed the package from the registry reportedly did not.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

What to do

Inferred

If you cloned antd-img-crop from GitHub and ran the build command recently, the report's logic says you should treat that machine as potentially compromised. Practical first steps: look for unfamiliar processes or persistence mechanisms, review any credentials or tokens used on that machine, and rotate them if in doubt.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Alleged

If you only ever installed the package from npm, the report places you outside the exposure path. A quick check of your lockfile to confirm nothing referenced the repository is still cheap peace of mind.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Confirmed and still uncertain

Alleged

On the known side, the report offers a short and clear list of claims: a forged commit in the repository, a malicious prebuild hook, delivery of Overlord RAT when the build ran, and no impact to the npm package. Each of those points comes from a single outlet's reporting, so far without independent corroboration in this batch.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Observed

The unknowns are substantial. The post says nothing about when the commit appeared, how it was introduced, who is behind it, how many developers actually built from source, or whether any real infections have been confirmed. Those gaps will determine how broad the response needs to be.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

What people are saying

Observed

The only voice in this evidence batch is TheHackersNews, which framed the finding bluntly: A routine code build could trigger a malware installation. The outlet also stressed the reassuring half of the story, stating that the npm package itself was not affected.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Observed

No maintainer statement, vendor advisory, or independent researcher commentary appears alongside the post. What the project's maintainers say next, and whether security firms publish indicators of compromise, will be the statements to watch.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Evolution

Observed

This batch captures the story at its opening beat. There is one public report, no earlier posts, and no follow-up yet, so the timeline so far is simply: discovery described, mechanism explained, and the npm package given the all-clear in the same breath.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Inferred

If the incident follows the usual arc for repository compromises, expect the forged commit to be removed, an advisory to follow, and detection guidance to surface. That is an expectation about how these cases typically unfold, not something the current evidence shows.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Reach

Observed

1 independent groups, 1 updates, and 1 engagements.

Technical detail

Inferred

The mechanism at the center of this story is the prebuild hook. Build tools let projects register scripts that execute at defined moments, and a prebuild script runs before compilation starts. That is what makes it attractive to attackers: the malicious code fires with the developer's privileges the instant the build command is issued, no extra click required.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Alleged

Applied to this case, the report claims the forged commit planted exactly such a hook in the antd-img-crop repository, that running npm run build set it off, and that the delivered payload was Overlord RAT. The npm registry copy of the package, per the same report, remained untouched.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Sources and evidence

Observed

This brief currently rests on a single item: a post on X by TheHackersNews summarizing its own coverage, with a link to the full article. That one post is the origin of every substantive claim here, including the forged commit, the hook mechanism, the RAT payload, and the clean npm package.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Observed

What the batch lacks is just as telling. There are no commit hashes, no timeline, no vendor or maintainer advisory, and no second source confirming the findings, so the appropriate stance is cautious: treat the report as a credible early warning, not as a closed case.TheHackersNewsx.com · TheHackersNews · xOpen original sourceSee in source list

Sources

  1. TheHackersNewsx.com · TheHackersNews · x

Incidents like this, every morning

The ones that need action first, in a 3-minute read.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Get the next one tomorrow morning

One email a day with what changed, what to fix first and how.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Share it with your team

Whoever handles security with you should get it too.

LinkedIn X

Your colleague gets a confirmation request. Nothing is sent unless they confirm.

See all news

Read also

Before you go: get this every day

The HIFY Radar daily edition lands every morning with the incidents that need action. Free.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click