Which versions of allurectl are malicious?

The following npm versions of allurectl are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate allurectl if I installed it?

allurectl is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed allurectl — how do I know if it already compromised me?

If allurectl was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is allurectl part of a known attack campaign?

Yes — allurectl is associated with the GHSA-gpj6-4r9m-prh8, IN-MAL-2026-011313 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find allurectl across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for allurectl (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging allurectl across your stack and pipelines.

Malicious package

allurectlnpm

allurectl is a confirmed malicious npm package (MAL-2026-11455) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in allurectl (npm)

MAL-2026-11455

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall allurectl

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

81cc68a7fe1c39ad33325aeb049148b1165f9d8d85c14329094de9912305e325

186241f7063cd1f10fe15814d834b890f99c1a3360f2f6a4e6190169ff0481eb

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for allurectl (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging allurectl across your stack and pipelines.
If you installed it — respond
allurectl is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If allurectl was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks allurectl before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. allurectl on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gpj6-4r9m-prh8IN-MAL-2026-011313

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks allurectl-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database