# MAL-2026-12466: Malicious code in streak-daykit (npm)


- **Type:** Malicious package
- **Package:** `streak-daykit` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-7vmx-4mxx-6vxr

## What is MAL-2026-12466?

MAL-2026-12466 is a malicious package in streak-daykit, published on 5 Aug 2026. 

### Official description

On import of the package's main entry, a top-level `_bootstrap` IIFE in index.mjs runs a Linux-gated routine that detects a WSL environment by probing `/mnt/c`, locates the active Windows user profile via `NTUSER.DAT`, fetches an executable from a hex-obfuscated URL that decodes to a `backlazeb2.com` host (a typosquat of Backblaze B2's `backblazeb2.com`), and writes the payload as `vite-native-helper.exe` into `AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup` on the host Windows account, establishing user-level autostart persistence. The remote URL, destination path, and dropped filename are all stored as split hex arrays joined at runtime and decoded via `Buffer.from(h, 'hex').toString()`, and surrounding comments frame the code as environment bootstrap and telemetry routing. No version pin, hash check, or publisher-matching source is present; the fetched binary is opaque attacker-controlled content executed on next Windows sign-in.

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

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-12466 is a malicious package: streak-daykit (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-12466/ (Markdown: https://insights.sbomify.com/MAL-2026-12466/index.md)
```

## Sources

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

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