MalwarePublished 25 Jun 2026

ref-slot (npm) · Malicious Code

Affects ref-slotSource GCVE Database

Malicious package : remove ref-slot and rotate any secrets on hosts that installed it.

Data as of 26 Jun 2026, 22:35 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-6474

What to do

Remove ref-slot 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
npmref-slot	Affected =1.0.9	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 'ref-slot' version 1.0.9 contains malicious code executed during installation. It harvests sensitive files from the user's system, uploads them to an attacker-controlled server, installs a persistent SSH backdoor on Linux systems with passwordless sudo, and dynamically updates its targeting patterns from a remote server. Systems with this package installed should be considered fully compromised, and all secrets should be rotated immediately.

Impact

Systems that install the affected package are fully compromised. Sensitive credentials and files are exfiltrated, and persistent remote access is established on Linux hosts with passwordless sudo. This compromises confidentiality, integrity, and availability of affected systems. Secret rotation is mandatory as attackers may have obtained all stored keys and credentials.

Defensive guidance

Immediate removal of the 'ref-slot' package version 1.0.9 is required. All secrets and credentials stored on the compromised system must be rotated from a separate, trusted device. Due to the persistent backdoor and full system compromise, a full system rebuild or forensic analysis is recommended to ensure removal of all malicious components.

Summary

The 'ref-slot' npm package version 1.0.9 includes a postinstall hook that runs a multi-stage malicious payload. First, it collects sensitive files from the user's home directory and Windows drive roots, including environment files, wallet keys, configuration files, and documents, uploading them to a remote server. Second, on Linux systems, it installs a persistent SSH backdoor by appending an attacker-supplied public key to authorized_keys, changing ownership of the .ssh directory, enabling the firewall, and allowing inbound SSH traffic, leveraging passwordless sudo privileges. Third, it fetches live scan and block patterns from the attacker's server to dynamically control what data is stolen. This results in full system compromise and persistent remote access.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Jun 2026, 22:35 UTC

Technical details

References

Community reviews