MAL-2026-4418 Malicious code in @pluxee-connect/api-client (npm)
Malicious package
Published
MAL-2026-4418 is a malicious package: @pluxee-connect/api-client (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-4418/ (Markdown: https://insights.sbomify.com/MAL-2026-4418/index.md)
- Package
- @pluxee-connect/api-client
- Registry
- npm
What is MAL-2026-4418?
MAL-2026-4418 is a malicious package in @pluxee-connect/api-client, published on 20 May 2026.
Official description
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.What should I do about MAL-2026-4418?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.
Sources
Also known as GHSA-wpmr-hxhp-4h27.