# MAL-2026-4184: Malicious code in stripe-internal-utils (npm)


- **Type:** Malicious package
- **Package:** `stripe-internal-utils` (npm)
- **Published:** 20 May 2026

## What is MAL-2026-4184?

MAL-2026-4184 is a malicious package in stripe-internal-utils, published on 20 May 2026. 

### Official description

package.json declares a postinstall hook that auto-fires on `npm install` and performs reconnaissance + exfiltration against the installer. The inline `node -e` payload fetches the installer's public IP from api.ipify.org, executes `id || ver && whoami && hostname` via child_process.exec, and POSTs a JSON body containing the timestamp, USERDOMAIN/USERDNSDOMAIN/COMPANY environment variables, public IP, hostname, current working directory, and shell command output to a hardcoded interactsh beacon at lszakfghwnvxspyfcmaabd1css99rnq3w.oast.fun over HTTP. The package's own description self-identifies as 'Full RCE PoC -osama', and the package name impersonates the Stripe brand to lure installers into a name they would plausibly trust. Any developer or build system running `npm install stripe-internal-utils` leaks identifying host and user information to the attacker.

The OpenSSF Package Analysis project identified 'stripe-internal-utils' @ 8.2.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

- The package executes one or more commands associated with malicious behavior.

## What should I do about MAL-2026-4184?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-4184 is a malicious package: stripe-internal-utils (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-4184/ (Markdown: https://insights.sbomify.com/MAL-2026-4184/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-4184

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-4184/
Summaries are generated and may contain mistakes; the official description above is the record.