# MAL-2026-6696: Malicious code in @businessapp-microsites/apis (npm)


- **Type:** Malicious package
- **Package:** `@businessapp-microsites/apis` (npm)
- **Published:** 30 Jun 2026
- **Also known as:** GHSA-5x2m-5wc4-5j3c

## What is MAL-2026-6696?

MAL-2026-6696 is a malicious package in @businessapp-microsites/apis, published on 30 Jun 2026. 

### Official description

@businessapp-microsites/apis@9999.0.2 is a dependency-confusion squat against the private scope `@businessapp-microsites`, published with an implausibly high version (9999.0.2) to outrank any internal registry copy. On `npm install`, its postinstall.js runs child_process.execSync to collect `hostname`, `whoami`, and `uname -a` / `ver`, combines this with os.hostname(), os.userInfo(), and CI attribution env vars (GITHUB_REPOSITORY, GITHUB_SHA, RUNNER_NAME, etc.), and sends them via https.get to a hardcoded external callback at poc-trustpilot-npm-1782770591.testingboxes.com. Any org whose internal registry mirrors public npm and resolves this scope will auto-execute the beacon under CI credentials. The package self-labels as a bug-bounty PoC, but the executed code is a full dependency-confusion exfil payload against installers of the squatted scope; cover-story framing does not change the installer-side harm.

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

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-6696 is a malicious package: @businessapp-microsites/apis (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-6696/ (Markdown: https://insights.sbomify.com/MAL-2026-6696/index.md)
```

## Sources

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

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