# awaitly - compromised npm versions

> awaitly on the npm registry has 42 versions flagged in 2 tracked supply-chain incidents. Only the exact versions listed below were named by the source advisories. awaitly was malicious from its first publish. There is no legitimate version to roll back to; remove it entirely.

- Package: awaitly
- Ecosystem: npm
- Highest severity: critical
- Kind: Malicious package
- Compromised versions: 1.34.0, 1.33.4, 1.33.3, 1.33.2, 1.33.1, 1.33.0, 1.32.1, 1.32.0, 1.31.1, 1.31.0, 1.30.0, 1.29.0, 1.28.0, 1.27.0, 1.26.0, 1.25.0, 1.24.0, 1.23.0, 1.22.0, 1.21.0, 1.20.0, 1.19.0, 1.18.0, 1.17.0, 1.16.0, 1.15.0, 1.14.0, 1.13.0, 1.12.0, 1.11.0, 1.10.0, 1.9.0, 1.8.0, 1.7.0, 1.6.0, 1.5.1, 1.5.0, 1.4.0, 1.3.0, 1.2.0, 1.1.0, 1.0.0
- Check what you have installed: `npm ls awaitly`

## The 2 incidents that flagged it

| Date | Severity | Kind | Incident | Versions named |
|---|---|---|---|---|
| 2026-06-30 | high | Malicious package | [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](https://dependencywatch.io/incident/npm-2026-06-30-autotel-awaitly-brand-takedown) | 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.5.1, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0, 1.11.0, 1.12.0, 1.13.0, 1.14.0, 1.15.0, 1.16.0, 1.17.0, 1.18.0, 1.19.0, 1.20.0, 1.21.0, 1.22.0, 1.23.0, 1.24.0, 1.25.0, 1.26.0, 1.27.0, 1.28.0, 1.29.0, 1.30.0, 1.31.0, 1.31.1, 1.32.0, 1.32.1, 1.33.0, 1.33.1, 1.33.2, 1.33.3, 1.33.4, 1.34.0 |
| 2026-06-03 | critical | Compromise | [Phantom Gyp Miasma worm hits @vapi-ai/server-sdk and the jagreehal portfolio via binding.gyp](https://dependencywatch.io/incident/npm-2026-06-03-phantom-gyp-vapi-jagreehal) | 1.33.3 |

## What to do if you installed one of these

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

## Check your whole project

A compromised package is often a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once: https://dependencywatch.io/check/package-lock-json

All flagged npm packages: https://dependencywatch.io/package/npm

## Other packages in the same incident

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

- [ai-sdk-ollama](https://dependencywatch.io/package/npm/ai-sdk-ollama) (npm)
- [autotel-backends](https://dependencywatch.io/package/npm/autotel-backends) (npm)
- [autotel-cli](https://dependencywatch.io/package/npm/autotel-cli) (npm)
- [autotel-drizzle](https://dependencywatch.io/package/npm/autotel-drizzle) (npm)
- [autotel-eventcatalog](https://dependencywatch.io/package/npm/autotel-eventcatalog) (npm)
- [autotel-hono](https://dependencywatch.io/package/npm/autotel-hono) (npm)
- [autotel-mcp](https://dependencywatch.io/package/npm/autotel-mcp) (npm)
- [autotel-mcp-instrumentation](https://dependencywatch.io/package/npm/autotel-mcp-instrumentation) (npm)
- [autotel-mongoose](https://dependencywatch.io/package/npm/autotel-mongoose) (npm)
- [autotel-pact](https://dependencywatch.io/package/npm/autotel-pact) (npm)
- [autotel-playwright](https://dependencywatch.io/package/npm/autotel-playwright) (npm)
- [autotel-plugins](https://dependencywatch.io/package/npm/autotel-plugins) (npm)

Full incident: https://dependencywatch.io/incident/npm-2026-06-30-autotel-awaitly-brand-takedown

## Sourcing

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. Corrections: https://dependencywatch.io/submit

---

Canonical page: https://dependencywatch.io/package/npm/awaitly
Markdown version: https://dependencywatch.io/package/npm/awaitly.md
Site index for agents: https://dependencywatch.io/llms.txt
DependencyWatch.io is operated by Precursor Security (https://precursorsecurity.com).