Supply Chain Incident

ua-parser-js npm package account compromise

Malicious versions of ua-parser-js were published to npm after maintainer account compromise, delivering credential-stealing and cryptomining payloads.

ConfidenceHigh
Evidence LevelVendor
Attack StageAccount Compromise
Source Artifact DivergenceNo

Executive Summary

Timeline

  1. Malicious versions disclosed

    The incident was publicly documented on the same date recorded for first observation and disclosure in the corpus.

Attack Chain

  1. Maintainer account compromise

    The compromise path is represented as account compromise because a package-registry maintainer account enabled malicious publication.

  2. Malicious npm publication

    The malicious versions were distributed through the npm registry under the ua-parser-js package name.

  3. Payload execution risk

    The recorded payload categories are credential theft and cryptomining, matching the incident's package-level impact model.

Affected Ecosystem

Defensive Lessons

Detection Notes

Open Questions

Affected Packages

Affected Releases

  • ua-parser-js@0.7.29 pkg:npm/ua-parser-js@0.7.29 · published 2021-10-22 Release
  • ua-parser-js@0.8.0 pkg:npm/ua-parser-js@0.8.0 · published 2021-10-22 Release
  • ua-parser-js@1.0.0 pkg:npm/ua-parser-js@1.0.0 · published 2021-10-22 Release

Repositories

No structured records.

Organizations

No structured records.

Maintainers

No structured records.

Threat Actors

No structured records.

Campaigns

No structured records.

Build Systems

No structured records.

Distribution Channels

  • npm registry

Compromised Accounts

  • ua-parser-js npm maintainer account

Connected Entities

  • npm registry Distribution Channel
  • ua-parser-js Package
  • ua-parser-js npm maintainer account Compromised Account
  • ua-parser-js@0.7.29 Release
  • ua-parser-js@0.8.0 Release
  • ua-parser-js@1.0.0 Release

References