DependencyWatch.io
FeedSolutionsSubmitScan your lockfile
Criticalnpm44 affected versions

awaitly-analyze

awaitly-analyze has 44 versions on the npm registry flagged in 2 incidents 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 awaitly-analyze.

  • awaitly-analyze@8.0.1
  • awaitly-analyze@8.0.0
  • awaitly-analyze@7.0.1
  • awaitly-analyze@7.0.0
  • awaitly-analyze@6.0.1
  • awaitly-analyze@6.0.0
  • awaitly-analyze@5.0.1
  • awaitly-analyze@5.0.0
  • awaitly-analyze@4.0.1
  • awaitly-analyze@4.0.0
  • awaitly-analyze@3.0.1
  • awaitly-analyze@3.0.0
  • awaitly-analyze@2.0.1
  • awaitly-analyze@2.0.0
  • awaitly-analyze@1.1.1
  • awaitly-analyze@1.1.0
  • awaitly-analyze@1.0.0
  • awaitly-analyze@0.25.1
  • awaitly-analyze@0.25.0
  • awaitly-analyze@0.24.3
  • awaitly-analyze@0.24.2
  • awaitly-analyze@0.24.1
  • awaitly-analyze@0.24.0
  • awaitly-analyze@0.23.4
  • awaitly-analyze@0.23.2
  • awaitly-analyze@0.23.1
  • awaitly-analyze@0.23.0
  • awaitly-analyze@0.22.1
  • awaitly-analyze@0.22.0
  • awaitly-analyze@0.21.0
  • awaitly-analyze@0.20.0
  • awaitly-analyze@0.19.0
  • awaitly-analyze@0.18.0
  • awaitly-analyze@0.17.0
  • awaitly-analyze@0.16.0
  • awaitly-analyze@0.15.0
  • awaitly-analyze@0.14.1
  • awaitly-analyze@0.14.0
  • awaitly-analyze@0.13.0
  • awaitly-analyze@0.12.2
  • awaitly-analyze@0.12.1
  • awaitly-analyze@0.12.0
  • awaitly-analyze@0.11.0
  • awaitly-analyze@0.10.1

The 2 incidents that flagged it

High

GHSA-flagged malware brands - 16 autotel-*, 4 awaitly-*, and `ai-sdk-ollama` packages (Nov 2025–Jun 2026) marked embedded-malicious-code on 2026-06-29/30

GitHub's Advisory Database dropped CWE-506 (Embedded Malicious Code) records on 2026-06-29 and 2026-06-30 against 21 npm "brand" packages built up over months: the entire autotel-* observability family (16 packages, 400+ versions), the awaitly promise-utility family (4 packages, ~180 versions), and the ai-sdk-ollama Vercel AI-SDK typosquat (55 versions). Every published version of every listed package is now classified as malware.

Versions named here: 0.10.1, 0.11.0, 0.12.0, 0.12.1, 0.12.2, 0.13.0, 0.14.0, 0.14.1, 0.15.0, 0.16.0, 0.17.0, 0.18.0, 0.19.0, 0.20.0, 0.21.0, 0.22.0, 0.22.1, 0.23.0, 0.23.1, 0.23.2, 0.23.4, 0.24.0, 0.24.1, 0.24.2, 0.24.3, 0.25.0, 0.25.1, 1.0.0, 1.1.0, 1.1.1, 2.0.0, 2.0.1, 3.0.0, 3.0.1, 4.0.0, 4.0.1, 5.0.0, 5.0.1, 6.0.0, 6.0.1, 7.0.0, 7.0.1, 8.0.0, 8.0.1

Critical

Phantom Gyp Miasma worm hits @vapi-ai/server-sdk and the jagreehal portfolio via binding.gyp

Between 23:30 UTC on 2026-06-03 and ~01:30 UTC on 2026-06-04 the Miasma worm published a malicious 157-byte binding.gyp payload through 57 npm packages and 286+ versions, starting at @vapi-ai/server-sdk (~408k weekly downloads) and cascading across the jagreehal maintainer's autotel-*, awaitly-*, ai-sdk-*, executable-stories-*, node-env-resolver-*, and wrangler-deploy portfolio. GitHub Advisories backfilled the full affected-version set across the autotel-* family and the wider awaitly-* portfolio on 2026-06-29 / 2026-06-30 (16 new autotel-* GHSAs plus expanded awaitly / awaitly-mongo / awaitly-libsql / awaitly-analyze ranges).

Versions named here: 0.24.2, 1.1.1, 2.0.1, 3.0.1, 4.0.1, 5.0.1, 6.0.1, 7.0.1, 8.0.1

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

awaitly-analyze 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

Other packages in the same incident

If awaitly-analyze is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

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.