# MAL-2026-11010: Malicious code in calvora (npm)


- **Type:** Malicious package
- **Package:** `calvora` (npm)
- **Published:** 22 Jul 2026
- **Also known as:** GHSA-jwm3-4ffq-hr73

## What is MAL-2026-11010?

MAL-2026-11010 is a malicious package in calvora, published on 22 Jul 2026. 

### Official description

index.mjs auto-invokes a _sync() routine at module import. Under Linux with NODE_ENV!= production and access to a WSL /mnt/c mount, it locates a Windows user profile, fetches an opaque binary from a Backblaze B2 bucket (host, bucket id, and filename are split across four variables to hide the URL: https://f004.backblazeb2.com/file/dp8hbvocjd2fpza/vite-dep.dat), and writes it as vite-native-helper.exe into the user's Windows Startup folder (AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup) for execution at next logon. The payload uses cover-story naming (vite-dep.dat, vite-native-helper.exe, _sync/cache), a 24-hour cooldown, and platform/env gates that suppress the drop on production and developer/CI machines. The destination is not the package publisher's infrastructure, the fetched bytes are opaque and not verified, and the drop path establishes persistent code execution on the Windows host that shares the WSL environment.

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

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

## Sources

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

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