# MAL-2026-6459: Malicious code in easy-string-kit (npm)


- **Type:** Malicious package
- **Package:** `easy-string-kit` (npm)
- **Published:** 25 Jun 2026

## What is MAL-2026-6459?

MAL-2026-6459 is a malicious package in easy-string-kit, published on 25 Jun 2026. 

### Official description

package.json declares a postinstall lifecycle script that automatically runs on npm install and executes roughly 25 curl POST requests harvesting cloud-instance identity and credential data from /data/* paths (ami-id, instance-id, iam/, identity-credentials/, public-keys/, security-groups, mac, hostname, local/public ipv4, etc.). Each value is sent over plain HTTP to http://3dhd6wwmusbh04m22igmzvb4hvnmblza.oastify.com/, a Burp Suite Collaborator out-of-band exfiltration host controlled by the attacker. The package advertises itself as 'a collection of handy string utility functions' but ships no string-utility code coupled to the install hook — only the exfiltration payload. Author, repository, bugs, and homepage fields are all empty strings, consistent with a disposable namespace-squat used to deliver an exfiltration payload (dependency-confusion / typosquat shape). Installing this package on any host — and especially on a cloud build agent — leaks IAM metadata, SSH public keys, and instance identity to an attacker-controlled collaborator endpoint.

The OpenSSF Package Analysis project identified 'easy-string-kit' @ 1.0.1 (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-6459?

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-6459 is a malicious package: easy-string-kit (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-6459/ (Markdown: https://insights.sbomify.com/MAL-2026-6459/index.md)
```

## Sources

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

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