Which versions of omglucidesotuff are malicious?

The following npm versions of omglucidesotuff are flagged malicious: 1.1.2, 2.0.0. Treat any of these as compromised.

How do I remediate omglucidesotuff if I installed it?

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

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

Yes — omglucidesotuff is associated with the GHSA-w7g9-q298-vp9x, IN-MAL-2026-010429, RLMA-2026-05586, RLUA-2026-06355 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 omglucidesotuff 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 omglucidesotuff (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging omglucidesotuff across your stack and pipelines.

Malicious package

omglucidesotuffnpm

omglucidesotuff is a confirmed malicious npm package (MAL-2026-10361) that executes malicious code on install (malicious versions 1.1.2, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in omglucidesotuff (npm)

MAL-2026-10361

Immediate action

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

npm uninstall omglucidesotuff

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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.

Malicious versions

2 flagged

1.1.22.0.0

Indicators of compromise (SHA-256)

471e4b0cb8b17f0677863d3d3b665b4e54cec5b194e58f699fcbbf9435888888

d144d98f0e90909ee371acfeeec0ad2ffe44450335ddf7f7a58f71a53dc7b107

70f1f0d7060151b6e475aac38df68118e713676be06a73286b304c6859a161c2

a7ec8b29c7b55b2ca9126f7c2f3493db98e212b2f1053ab78ce0f9f1f7531dd8

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

Campaign

GHSA-w7g9-q298-vp9xIN-MAL-2026-010429RLMA-2026-05586RLUA-2026-06355

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks omglucidesotuff-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