Which versions of logform-core are malicious?

The following npm versions of logform-core are flagged malicious: 3.1.0, 3.2.0, 3.3.0. Treat any of these as compromised.

How do I remediate logform-core if I installed it?

logform-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed logform-core — how do I know if it already compromised me?

If logform-core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is logform-core part of a known attack campaign?

Yes — logform-core is associated with the GHSA-f2wx-p6h3-rgg2, IN-MAL-2026-013248, IN-MAL-2026-012957, IN-MAL-2026-013001 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find logform-core across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for logform-core (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging logform-core across your stack and pipelines.

Malicious package

logform-corenpm

logform-core is a confirmed malicious npm package (MAL-2026-11328) that steals credentials and exfiltrates sensitive data (malicious versions 3.1.0, 3.2.0, 3.3.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in logform-core (npm)

MAL-2026-11328

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall logform-core

What this malware does

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.

Malicious versions

3 flagged

3.1.03.2.03.3.0

Indicators of compromise (SHA-256)

4e18f24df37ad0cd0ddd311e006738521585804f186b83c814cbbc3af20aecff

c56b840ff0fbbaf197d07511638db31b76600e185d0b4a988cc20848d96566f4

1ec6c47e9e94b571242404a22ce01e255dc1df012c3d13477b5d2db9a96a037c

a9ed16b42c92990afda7814f1cdd84a7c4e2d21018466716f13aa5336992d6d4

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for logform-core (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging logform-core across your stack and pipelines.
If you installed it — respond
logform-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If logform-core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks logform-core before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. logform-core on npm has been identified as a malicious package (versions 3.1.0, 3.2.0, 3.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-f2wx-p6h3-rgg2IN-MAL-2026-013248IN-MAL-2026-012957IN-MAL-2026-013001

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks logform-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database