Which versions of ugc-kit are malicious?

The following npm versions of ugc-kit are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate ugc-kit if I installed it?

Remove ugc-kit 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 ugc-kit — how do I know if it already compromised me?

If ugc-kit 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 ugc-kit part of a known attack campaign?

Yes — ugc-kit is associated with the GHSA-v4w5-3vhx-g64x 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 ugc-kit 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 ugc-kit (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ugc-kit across your stack and pipelines.

Malicious package

ugc-kitnpm

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

MAL-2025-192951

Immediate action

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

npm uninstall ugc-kit

What this malware does

The package ugc-kit 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 'ugc-kit' @ 99.99.99 (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

99.99.99

Indicators of compromise (SHA-256)

78255cc2dc6c1a0b4d77756828a287e13391c46cfb67f0632a013725de6efeca

2ffd0991cb1cc7098930838b404210022aa2667d78f2884417f449d85e90fb12

4e44ecda4e96910709480e50046146e482992e36fb2e8429211e1f653376d123

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 ugc-kit (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ugc-kit across your stack and pipelines.
If you installed it — respond
Remove ugc-kit 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 ugc-kit 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 ugc-kit 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. ugc-kit on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-v4w5-3vhx-g64x

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks ugc-kit-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