Which versions of undicy-lint are malicious?

The following npm versions of undicy-lint are flagged malicious: 7.23.1. Treat any of these as compromised.

How do I remediate undicy-lint if I installed it?

Remove undicy-lint from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed undicy-lint — how do I know if it already compromised me?

If undicy-lint was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is undicy-lint part of a known attack campaign?

Yes — undicy-lint is associated with the GHSA-g752-q3r2-xhrj 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 undicy-lint across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for undicy-lint (version 7.23.1).

Malicious package

undicy-lintnpm

Advisory published Feb 26, 2026Updated Mar 2, 2026

undicy-lint is a confirmed malicious npm package (MAL-2026-1056) that executes malicious code on install (malicious version 7.23.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in undicy-lint (npm)

MAL-2026-1056

Immediate action

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

npm uninstall undicy-lint

What this malware does

The package undicy-lint was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'undicy-lint' @ 7.23.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

7.23.1

Indicators of compromise (SHA-256)

49c23e1d7e0cb34c37951701004af5b53d9ed82fced58df47554dd6c7eee6213

3e5df89180b140f5106db0b74f5ee04330236214094173880f7baf0fd47088a8

2713794393ff885438b3aa1cc6dc97cff34cd42825c28e917bf8ec24ee704ff7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for undicy-lint (version 7.23.1).
If you installed it — respond
Remove undicy-lint from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If undicy-lint was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. undicy-lint on npm has been identified as a malicious package (version 7.23.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g752-q3r2-xhrj

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks undicy-lint-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database