@pluxee-connect/api-clientnpm
Advisory published Updated
@pluxee-connect/api-client is a confirmed malicious npm package (MAL-2026-4418) that opens a backdoor for remote access (malicious versions 99.0.0, 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @pluxee-connect/api-client (npm)
What this malware does
On npm install, postinstall.js collects os.hostname(), os.userInfo(), and process.version and transmits them over plain HTTP to 716bw4e4k31qif2nc1v658fb62ct0soh.oastify.com (a Burp Collaborator out-of-band interaction subdomain), with DNS resolution providing a second exfil channel via subdomain encoding. The package itself is a near-empty shell — index.js exports only a ConsentsStatus enum — and is published at version 99.0.1, far above any plausible legitimate release for the @pluxee-connect scope. The structural shape (high-bumped version + trivial functional surface + lifecycle-time OOB beacon to oastify.com) is the canonical dependency-confusion attack against an internal scope. Any developer or CI system that resolves @pluxee-connect/api-client from public npm will leak machine identifiers to the attacker.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for @pluxee-connect/api-client (2 malicious versions).
If you installed it — respond
@pluxee-connect/api-client establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @pluxee-connect/api-client was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks @pluxee-connect/api-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.