GCVE-110-OSM-2026-4382

This package was republished without maintainer authorization during a large-scale account takeover of the npm publisher account `atool`, attributed to the threat actor TeamPCP. On 2026-05-19 the `atool` account -- which owns 547 packages including the entire AntV (Alibaba) data-visualization suite -- pushed new versions of 315 packages in two tightly clustered publish waves, producing 633 package@version artifacts in a single day across many unrelated source repositories. This signature matches an automated `npm publish` loop running against a stolen publishing credential, and the republished tarballs beacon to attacker-controlled C2 infrastructure disguised as an OpenTelemetry trace collector. The affected packages combine for over 16 million weekly downloads. Any version of this package published on or after 2026-05-19T01:39:31Z must be treated as compromised. === PAYLOAD: npm maintainer account takeover -- "mini-shai-hulud" mass republish === Compromised maintainer account : atool (npm) Threat actor : TeamPCP Attack vector : stolen/phished npm publishing credential or leaked automation/CI token Affected versions of this package (republished by the compromised account): 0.2.2, 0.3.2 Mass-publish waves (UTC): Wave 1 : 2026-05-19T01:39:31Z - 2026-05-19T01:56:46Z (317 versions) Wave 2 : 2026-05-19T02:05:59Z - 2026-05-19T02:06:05Z (314 versions in a ~6s burst) Command-and-control / exfiltration infrastructure: Domain : t.m-kosche.com C2 URL : https://t.m-kosche.com:443/api/public/otel/v1/traces IP : 185.95.159.32 Behavior: The attacker republished fresh versions across 315 packages owned by the `atool` account in two coordinated bursts. The injected payload beacons to an attacker-controlled endpoint disguised as an OpenTelemetry trace collector (/api/public/otel/v1/traces) to blend exfiltration traffic with legitimate telemetry. Treat every listed version as compromised. Remediation: pin to a version published before 2026-05-19T01:39:31Z; audit lockfiles and CI caches for the affected versions; install with --ignore-scripts; block t.m-kosche.com and 185.95.159.32 at the network egress; rotate any npm tokens or environment secrets exposed to builds that resolved an affected version.