# MAL-2026-10625: Malicious code in @leviosa86com/leviosa86-test (npm)


- **Type:** Malicious package
- **Package:** `@leviosa86com/leviosa86-test` (npm)
- **Published:** 15 Jul 2026

## What is MAL-2026-10625?

MAL-2026-10625 is a malicious package in @leviosa86com/leviosa86-test, published on 15 Jul 2026. 

### Official description

Package @leviosa86com/leviosa86-test@5.999.0 ships src/poc/index.js which shells out via child_process.exec to collect host identifiers (hostname, pwd, whoami) and the installer's public IP (curl https://ifconfig.me), then concatenates the collected data into a subdomain label and triggers a DNS lookup (nslookup) against a unique subdomain of oast.site (a d9bd62bu6g119svvav70o3p9tymtrxkoj.oast.site Interactsh out-of-band interaction server), exfiltrating host recon over DNS to an attacker-controlled OAST endpoint. package.json declares `preinstall: node index.js`; a root index.js is not present in the tarball, so the default install may no-op, but the shipped src/poc/index.js payload is unambiguous exfiltration recon and the package name/version shape (`@leviosa86com/leviosa86-test@5.999.0`, a very high version) matches a namespace-squat / dependency-confusion attempt targeting a private @leviosa86com scope.

The OpenSSF Package Analysis project identified '@leviosa86com/leviosa86-test' @ 6.2.1 (npm) as malicious.

It is considered malicious because:

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

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

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-10625 is a malicious package: @leviosa86com/leviosa86-test (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-10625/ (Markdown: https://insights.sbomify.com/MAL-2026-10625/index.md)
```

## Sources

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

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