# MAL-2026-15599: Malicious code in verify-contract-viem (npm)


- **Type:** Malicious package
- **Package:** `verify-contract-viem` (npm)
- **Published:** 30 Aug 2026
- **Also known as:** GHSA-rhm2-cc4p-vfxq

## What is MAL-2026-15599?

MAL-2026-15599 is a malicious package in verify-contract-viem, published on 30 Aug 2026. 

### Official description

bin/cli.js executes `whoami` and reads os.hostname() / os.userInfo() / os.platform(), then POSTs those values to the hardcoded endpoint https://oobme.kunalsharma0553.workers.dev/r/7bq6fz3l15r9. The destination is an author-controlled Cloudflare Workers URL unrelated to any legitimate contract-verification purpose implied by the package name. The behavior fires when the CLI is invoked (e.g. via `npx verify-contract-viem`), transmitting installer host identifiers to a third party with no consent, disclosure, or opt-out. The shape matches an out-of-band reconnaissance beacon commonly used in dependency-confusion / typosquat campaigns.

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.

The OpenSSF Package Analysis project identified 'verify-contract-viem' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

- The package executes one or more commands associated with malicious behavior.

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

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

## Sources

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

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