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

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

Malicious package

undicy-lintnpm

Malicious code in undicy-lint (npm) Remove it immediately and rotate any exposed credentials.

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for undicy-lint (version 7.23.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging undicy-lint across your stack and pipelines.
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 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 undicy-lint 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. 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