MalwarePublished 26 Aug 2026Updated 29 Oct 2026

@worrisome/reutil (npm) · Malicious Code

Affects @worrisome/reutilSource GCVE Database

Malicious package : remove @worrisome/reutil and rotate any secrets on hosts that installed it.

Data as of 29 Oct 2026, 18:24 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-15604

What to do

Remove @worrisome/reutil from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@worrisome/reutil	Affected 1.0.0 – 1.0.5 5 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package @worrisome/reutil is a malicious package used as part of a phishing campaign that hosts a fake Cloudflare Turnstile verification page. The package contains only an index.html file that, when opened in a browser, decrypts a redirect URL and navigates the user to a phishing site. It does not execute malicious code during npm install or affect the installing machine directly. The abuse involves using the npm registry as a static file host for phishing landing pages, targeting users who open the HTML in a browser rather than developers installing the package.

Impact

This package does not compromise the security of machines that install it via npm, as it does not execute code during installation or runtime in Node.js environments. However, it poses a phishing risk to users who open the index.html file in a browser, as it redirects them to attacker-controlled phishing sites, including typosquatted Microsoft login pages and ChatGPT redirects. The threat targets human victims who interact with the phishing page rather than developers or automated systems. There is no evidence of direct exploitation or malware execution on the installer's system.

Defensive guidance

Since the package does not execute malicious code during installation and is used solely as a static phishing page host, the primary mitigation is to avoid opening the index.html file or URLs pointing to this package in a browser. Developers and users should remove the package if installed and avoid using untrusted npm packages, especially those with suspicious or single-purpose content. No action is required to secure the installing machine beyond standard security practices, as the package does not compromise it.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 18:24 UTC

Technical details

References

Community reviews