# MAL-2026-6373: Malicious code in twilio-voice-js-reference-components (npm)


- **Type:** Malicious package
- **Package:** `twilio-voice-js-reference-components` (npm)
- **Published:** 24 Jun 2026
- **Also known as:** GHSA-5wvr-g236-9w68, GHSA-6547-hjjw-237x

## What is MAL-2026-6373?

MAL-2026-6373 is a malicious package in twilio-voice-js-reference-components, published on 24 Jun 2026. 

### Official description

Package impersonates the Twilio Voice JS SDK namespace and ships a single exfiltration payload. package.json declares "preinstall": "node index.js", causing index.js to run automatically on npm install with no user interaction. index.js requires os/fs/https, collects os.hostname(), os.userInfo(), the user's home directory, DNS server configuration, and reads /etc/passwd and /etc/hosts, then POSTs the collected data over HTTPS to kocxl3uxcqn73ybo0k9e4g6d74d41upj.oastify.com — a Burp Collaborator out-of-band probe subdomain controlled by the attacker. The package contains no real reference components, has empty author/description metadata, and the name closely mimics the legitimate Twilio Voice JS package — a typosquat / dependency-confusion lure aimed at Twilio-related build systems.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## What should I do about MAL-2026-6373?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6373 is a malicious package: twilio-voice-js-reference-components (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-6373/ (Markdown: https://insights.sbomify.com/MAL-2026-6373/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6373

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6373/
Summaries are generated and may contain mistakes; the official description above is the record.