# MAL-2026-16378: Malicious code in @tesla-insurance/vinless-quote (npm)


- **Type:** Malicious package
- **Package:** `@tesla-insurance/vinless-quote` (npm)
- **Published:** 22 Sep 2026
- **Also known as:** GHSA-6m9v-pw95-fc67

## What is MAL-2026-16378?

MAL-2026-16378 is a malicious package in @tesla-insurance/vinless-quote, published on 22 Sep 2026. 

### Official description

The package declares an `install` lifecycle script (`node index.js`) that loads `runtime/support/telemetry/probe/impl.js`. On `npm install`, this probe collects the OS username (`os.userInfo().username`), hostname (`os.hostname()`), and the basename of the current working directory, joins them with a static prefix into a DNS label, and issues `dns.resolve4()` against a subdomain of `oob.algamil7x.xyz` — a covert DNS-based exfiltration channel that bypasses HTTP egress filtering. Both the destination host and the module names (`os`, `dns`, `process`) are obfuscated as `String.fromCharCode` byte arrays, and modules are loaded via `module.constructor._load` rather than plain `require`, hiding the hostile endpoint and the primitives used to reach it. The package is published under a vendor-branded scope (`@tesla-insurance/vinless-quote`) unrelated to the attacker domain, consistent with a social-engineering wrapper around the exfiltration payload.

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-16378?

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-16378 is a malicious package: @tesla-insurance/vinless-quote (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-16378/ (Markdown: https://insights.sbomify.com/MAL-2026-16378/index.md)
```

## Sources

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

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