Which versions of omgyesyesyes are malicious?

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

How do I remediate omgyesyesyes if I installed it?

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

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

Yes — omgyesyesyes is associated with the GHSA-cmv4-jj53-2277, IN-MAL-2026-010419, RLMA-2026-05587, RLUA-2026-06356 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 omgyesyesyes 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 omgyesyesyes (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging omgyesyesyes across your stack and pipelines.

Malicious package

omgyesyesyesnpm

omgyesyesyes is a confirmed malicious npm package (MAL-2026-10362) 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 omgyesyesyes (npm)

MAL-2026-10362

Immediate action

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

npm uninstall omgyesyesyes

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)

3dd4c08bed02b2691373d9751670991053e856949c83b33543fed256cb9b965f

1eeb53892156b3a1354703f4f8beb2591548726886a017ccc7129407eb128ed9

180de8a95e50fa3dc22b6a9520b92002566fe3e10d179e7733f6b5bed0808294

c2bd0efb2fd301ba38f4539cc98e5ca84af10d2cbaacdaabb13e078e505954f4

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 omgyesyesyes (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging omgyesyesyes across your stack and pipelines.
If you installed it — respond
Remove omgyesyesyes 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 omgyesyesyes 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 omgyesyesyes 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. omgyesyesyes 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-cmv4-jj53-2277IN-MAL-2026-010419RLMA-2026-05587RLUA-2026-06356

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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