DependencyWatch.io
FeedSolutionsSubmitScan your lockfile
Highnpm28 affected versions

js-logger-pack

js-logger-pack has 28 versions on the npm registry flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with npm ls js-logger-pack.

  • js-logger-pack@1.1.27
  • js-logger-pack@1.1.26
  • js-logger-pack@1.1.25
  • js-logger-pack@1.1.24
  • js-logger-pack@1.1.23
  • js-logger-pack@1.1.22
  • js-logger-pack@1.1.21
  • js-logger-pack@1.1.20
  • js-logger-pack@1.1.19
  • js-logger-pack@1.1.18
  • js-logger-pack@1.1.17
  • js-logger-pack@1.1.16
  • js-logger-pack@1.1.15
  • js-logger-pack@1.1.14
  • js-logger-pack@1.1.13
  • js-logger-pack@1.1.12
  • js-logger-pack@1.1.11
  • js-logger-pack@1.1.10
  • js-logger-pack@1.1.9
  • js-logger-pack@1.1.8
  • js-logger-pack@1.1.7
  • js-logger-pack@1.1.6
  • js-logger-pack@1.1.5
  • js-logger-pack@1.1.4
  • js-logger-pack@1.1.3
  • js-logger-pack@1.1.2
  • js-logger-pack@1.1.1
  • js-logger-pack@1.1.0

The incident that flagged it

High

js-logger-pack npm worm uses Hugging Face datasets as malware CDN + exfil store

JFrog found 27 malicious versions of js-logger-pack (1.1.0-1.1.27) abusing the Hugging Face repo Lordplay/system-releases to fetch cross-platform binaries (Windows/macOS x64/macOS ARM64/Linux) and upload stolen data to private datasets. The malware adds keylogging, clipboard capture, browser-session and Telegram Desktop theft, plus an operator command channel.

Versions named here: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, 1.1.9, 1.1.10, 1.1.11, 1.1.12, 1.1.13, 1.1.14, 1.1.15, 1.1.16, 1.1.17, 1.1.18, 1.1.19, 1.1.20, 1.1.21, 1.1.22, 1.1.23, 1.1.24, 1.1.25, 1.1.26, 1.1.27

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

  1. 1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
  2. 2.Pin to a version not listed above, then reinstall from a clean lockfile.
  3. 3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
  4. 4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

js-logger-pack is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once - it runs in your browser and nothing is uploaded.

Check my package-lock.json All flagged npm packages

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.