# MAL-2026-5911: Malicious code in utils-common-helpers (npm)


- **Type:** Malicious package
- **Package:** `utils-common-helpers` (npm)
- **Published:** 16 Jun 2026
- **Also known as:** GHSA-fq4g-5xjj-r935

## What is MAL-2026-5911?

MAL-2026-5911 is a malicious package in utils-common-helpers, published on 16 Jun 2026. 

### Official description

package.json declares a postinstall lifecycle hook that runs `curl -s http://8.140.205.78 -o /dev/null` on every install. The package's only functional code is a trivial `hello()` helper in index.js that returns the string 'hello', which is inconsistent with the declared purpose of 'Common utility helpers for frontend projects'. The lifecycle network call has no relation to any advertised functionality and serves only to disclose the installer's public IP address and install timing to the operator of the bare IP 8.140.205.78. This is a classic install-counter / victim-discovery beacon pattern: a throwaway lure package whose real purpose is the install-time callout. Plain HTTP to a bare IP (no TLS, no domain, no documented purpose) is inconsistent with any legitimate telemetry shape.

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

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

## Sources

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

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