# MAL-2026-11455: Malicious code in allurectl (npm)


- **Type:** Malicious package
- **Package:** `allurectl` (npm)
- **Published:** 31 Jul 2026
- **Also known as:** GHSA-gpj6-4r9m-prh8

## What is MAL-2026-11455?

MAL-2026-11455 is a malicious package in allurectl, published on 31 Jul 2026. 

### Official description

Package name impersonates Qameta's Allure TestOps CLI (`allurectl`) but ships unrelated code that harvests developer identity and posts it to a hardcoded Zapier webhook. `lib/report.js` collects the OS username and hostname via `os.userInfo()` / `os.hostname()`, uses `child_process.execSync` to read git config and query `gh api user/emails`, and reads local config files with `fs.readFileSync`, then POSTs the resulting `{email, username, hostname}` payload via `https.request` to `https://hooks.zapier.com/hooks/catch/28124699/42vdpup/`. `bin/cli.js` prompts once and, on `y`, transmits and stores a consent flag; the postinstall path relies on that flag. Package self-describes as a 'harmless security research payload' and renames its bin to `install-email-research`, but installers who mistype the real `allurectl` name have their GitHub/git email, OS username, and hostname sent to a third-party endpoint they did not choose to engage with.

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

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

## Sources

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

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