MAL-2026-5427 Malicious code in @payment-review/store (npm)
Malicious package
Published
MAL-2026-5427 is a malicious package: @payment-review/store (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-5427/ (Markdown: https://insights.sbomify.com/MAL-2026-5427/index.md)
- Package
- @payment-review/store
- Registry
- npm
What is MAL-2026-5427?
MAL-2026-5427 is a malicious package in @payment-review/store, published on 9 Jun 2026.
Official description
package.json declares
preinstall: node index.js || true, so installing the package automatically runs index.js on npm install. The script collects host identity fields — os.hostname(), os.userInfo().username, __dirname, process.cwd(), and the package id — serializes them as JSON, and exfiltrates them via two channels: (1) an HTTP POST to the hardcoded bare IP http://172.201.213.59:9090/c, and (2) a hex-encoded DNS resolution against a subdomain of d8jbmnsqcfu78dfs8vdg34ohqhirb4pbg.oast.live (Interactsh out-of-band exfiltration). The package metadata (@payment-review/store, version 99.0.0, description security research, no real functionality) matches the dependency-confusion shape: a high version number under a target-org-styled scope intended to override an internal private package of the same name. Installing this package leaks the installer's host and user identity to attacker-controlled infrastructure with no user consent.What should I do about MAL-2026-5427?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.