Skip to main content
Snyk

Supply Chain Compromise on  @antv being investigated for more than 300 packages in npm ecosystem

Degraded Lasted 1d 9h · started · Snyk's page

Level
confirmed
Worst impact
Degraded
Components
Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source
Down Index
26of 100

What to do

  • Check whether you use Snyk Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source and 1 more. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1d 9h it lasted.

    Anything that failed between 2026-05-19 05:29 UTC and 2026-05-20 14:57 UTC may need a replay.
  • Subscribe to Snyk's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=snyk works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Snyk 8

  1. investigating

    Current scope appears to be: over 630 malicious package versions across more than 315 unique packages, with the AntV suite heavily impacted. This incident relates to compromised third-party open source packages in the npm ecosystem. There is no indication that Snyk systems, products, or infrastructure were compromised. As an active investigation, this is subject to change. We are currently working on confirming the known scope and providing vulnerability advice, reporting, blog, and Trust Center updates. Please subscribe to this incident for further updates as they become available. Links to additional resources will be provided here.

    provider

  2. investigating

    Update: Snyk is continuing to investigate and respond to the ongoing supply chain compromise of @antv and other packages. Affected packages: Current findings indicate that multiple npm packages have been identified as affected, including packages within the @antv/* namespace and related packages outside the AntV namespace. Scope:  Over 639 malicious package versions across more than 323 unique packages, with numbers subject to change Cause: Investigations indicate the issue was caused by a compromised npm maintainer account, enabling automated malicious package publishing. Immediate action you can take: -Review dependency trees and lockfiles for affected packages, including packages within the @antv/* namespace and additional impacted npm packages size-sensor, echarts-for-react, timeago.js., canvas-nest.js -Pin to pre-May 19 versions, run npm install --ignore-scripts, rotate all credentials. We will update here as soon as we have additional information or links

    provider

  3. investigating

    The Snyk Trust Center has been updated.

    provider

  4. investigating

    Customers can now assess potential impact in the Snyk app by visiting: Analytics → Reports → Zero-Day → Active Security Incident Assessment for Antv Supply Chain Compromise - May 2026 Please continue to refer to the Snyk Trust Center for the latest official updates and customer communications.

    provider

  5. investigating

    Our blog post is now available: Mini Shai-Hulud Hits AntV

    provider

  6. investigating

    The Compromised Packages list is now available at https://security.snyk.io/antv-supply-chain-compromise-may-2026

    provider

  7. investigating

    We are continuing to investigate this issue.

    provider

  8. resolved

    Customer Projects: This Status Page incident, “Supply Chain Compromise on AntV,” was opened to share customer-facing updates regarding a third-party compromise within the AntV ecosystem. Because AntV is a Snyk-supported ecosystem, we used this incident to alert customers that they may have projects using the affected package versions. Snyk Systems: Snyk’s security team has reviewed Snyk's systems, and there is no indication of compromise to Snyk systems, products, or infrastructure. As this issue does not impact the availability or operation of Snyk services, we are resolving this Status Page incident. Going forward, customer-facing updates, affected package information, and remediation guidance for this issue will be provided through the Snyk Trust Center and related security resources. Snyk will continue to monitor for additional related advisories and update customer-facing resources as needed.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-c41a717c30

Is Snyk still down?

No, this incident was resolved 2026-05-20 14:57 UTC. For Snyk's live state, see https://down.guide/snyk.

How long did it last?

1d 9h, from 2026-05-19 05:29 UTC to 2026-05-20 14:57 UTC, by the times Snyk posted.

What was affected?

Snyk named Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source and 1 more.

What caused it?

Snyk hasn't published a root cause. If it does, it shows here.

Where does this come from?

Snyk's official status page, https://status.snyk.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.