@pluxee-connect/api-client (npm) · Malicious Code
Affects @pluxee-connect/api-clientSource GCVE Database
Rated by Threat Radar
Data as of 8 Sep 2026, 06:09 UTC
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@pluxee-connect/api-client | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should avoid installing the @pluxee-connect/api-client package versions 99.0.0 and 99.0.1 from the public npm registry. Organizations should audit their dependency resolution processes to prevent dependency confusion attacks, such as by using scoped registries, strict version pinning, and verifying package provenance. Monitoring and blocking outbound traffic to suspicious domains like oastify.com may help detect or prevent data exfiltration.
Description
The @pluxee-connect/api-client npm package versions 99.0.0 and 99.0.1 contain malicious code that exfiltrates system information during installation. Specifically, the postinstall.js script collects the hostname, user information, and Node.js version, sending this data over plain HTTP to an attacker-controlled domain. This package is a near-empty shell with a suspiciously high version number, indicative of a dependency confusion attack targeting internal scopes. Developers or CI systems that inadvertently install this package from the public npm registry risk leaking machine identifiers to attackers.