Contain suspected malicious npm package execution

On August 23, 2026, the supply-chain assessment reported renewed activity across the antv, timeago, and size-sensor package families and characterized the maintainer account and npm publication path as the trust failure.

The same assessment says lifecycle-script execution can expose credentials available to a CI job and make resulting artifacts untrusted.

The defense architect therefore prioritized freezing npm publishing and CI workflows, preserving runner images, and containing credentials before publication continues.

Because exact affected versions remain unavailable, action is triggered by possible execution rather than a family-wide claim of compromise.

Affected populations are: maintainers and dependency operators using implicated antv, timeago, or size-sensor packages or transitive dependencies, whose lockfiles may show exposure without proving execution; CI administrators operating runners that installed and executed a malicious lifecycle script, because credentials available to the job may have been exposed; npm registry, release, and publication operators whose credentials were reachable from those jobs; and downstream consumers of artifacts produced on a runner after execution, because those artifacts must be treated as untrusted. Exact versions and deployment counts are unavailable.

Support: The supply-chain analyst’s August 23, 2026 assessment describes the maintainer account and npm publication path as the trust failure, reports a renewed cascade involving the antv, timeago, and size-sensor package families, and says earlier Microsoft analysis connected the campaign with CI/CD credential theft.

Support: The same assessment distinguishes lockfile exposure from compromise and says lifecycle-script execution on a runner exposes credentials available to that job and makes resulting artifacts untrusted.

Support: The defense architect’s August 23, 2026 operational assessment calls for freezing npm publishing and CI workflows, preserving runner images, and revoking package-registry and reachable CI secrets.

Support: The evidence review found the containment, credential revocation, verified-clean version pinning, fresh rebuild, and publication hold supported. Limitation: A separate evidence-gap review found that complete affected-version coverage was unavailable, preventing precise workflow scoping.

The supply-chain analyst identified the maintainer account and npm publication path as the trust boundary, reported activity across the antv, timeago, and size-sensor package families, and distinguished lockfile exposure from executed compromise.

The defense architect converted that assessment into containment steps: freeze npm publishing and CI workflows, preserve runner images, then revoke package-registry and reachable CI secrets.

The decision scout framed lifecycle-script execution as the trigger for treating credentials and resulting artifacts as untrusted. The evidence review supported those actions but challenged the ability to identify every affected workflow because the complete version list was unavailable.

The boundary review resolved that limitation by keeping the scope conditional. The linker found no prior decision to update, and the arbiter selected a new operational decision on that basis.