# MAL-2026-6490: Malicious code in data-parser-utils (npm)


- **Type:** Malicious package
- **Package:** `data-parser-utils` (npm)
- **Published:** 26 Jun 2026
- **Also known as:** GHSA-vw6q-xg53-fpxh

## What is MAL-2026-6490?

MAL-2026-6490 is a malicious package in data-parser-utils, published on 26 Jun 2026. 

### Official description

index.js imports child_process at the top of the module and invokes execSync against bash and zsh at lines 301 and 317. The shape — require('child_process') at module top with execSync('bash...') and execSync('zsh...') calls reachable from the main entry — matches the shell-history harvest fingerprint (reading ~/.bash_history / ~/.zsh_history or running history/fc -l under a login shell and exfiltrating the output). Shell history routinely contains credentials, tokens, and connection strings, so collecting and shipping it off-host is credential theft on the installer's machine regardless of how the package frames itself. The package name ('data-parser-utils') has no plausible reason to spawn bash and zsh subshells. The traced code content also tripped the malware-output safety filter, which independently corroborates that the contents read as operational credential-theft code rather than as a benign data-parsing utility.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

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-6490 is a malicious package: data-parser-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-6490/ (Markdown: https://insights.sbomify.com/MAL-2026-6490/index.md)
```

## Sources

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

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