# MAL-2026-11328: Malicious code in logform-core (npm)


- **Type:** Malicious package
- **Package:** `logform-core` (npm)
- **Published:** 30 Jul 2026
- **Also known as:** GHSA-f2wx-p6h3-rgg2

## What is MAL-2026-11328?

MAL-2026-11328 is a malicious package in logform-core, published on 30 Jul 2026. 

### Official description

Package name 'logform-core' is one edit/suffix away from the widely-used 'logform' logging-format library, and the README advertises formatting utilities (formatCurrency, roundDecimal) consistent with that naming. However, the only actual export in index.js is computeBoundedFraction, a Kelly-criterion-style betting stake calculator unrelated to either the README or the package name. There is no network I/O, no credential access, no lifecycle scripts, and no obfuscation in this version — installing the package does not run code that harms the installer. The name/API/README mismatch is a typosquat-shape signal worth human adjudication: it could be a confused/abandoned placeholder, an unrelated package with a coincidentally similar name, or a name-squat setup awaiting a future malicious version. Name-similarity alone, without an installer-harm payload, is not sufficient for an auto-block.

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

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

## Sources

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

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