Which versions of @yuva2210/okx-poc-preinstall are malicious?

The following npm versions of @yuva2210/okx-poc-preinstall are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate @yuva2210/okx-poc-preinstall if I installed it?

Remove @yuva2210/okx-poc-preinstall 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 @yuva2210/okx-poc-preinstall — how do I know if it already compromised me?

If @yuva2210/okx-poc-preinstall 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 @yuva2210/okx-poc-preinstall part of a known attack campaign?

Yes — @yuva2210/okx-poc-preinstall is associated with the RLMA-2026-10657 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 @yuva2210/okx-poc-preinstall across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @yuva2210/okx-poc-preinstall (2 malicious versions).

Malicious package

@yuva2210/okx-poc-preinstallnpm

Advisory published Sep 22, 2026Updated Sep 24, 2026

@yuva2210/okx-poc-preinstall is a confirmed malicious npm package (MAL-2026-16531) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @yuva2210/okx-poc-preinstall (npm)

MAL-2026-16531

Immediate action

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

npm uninstall @yuva2210/okx-poc-preinstall

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

4c724c99f1210929d6a6fd373898f330a73434b48a36474ad0d4a4ef4929632c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @yuva2210/okx-poc-preinstall (2 malicious versions).
If you installed it — respond
Remove @yuva2210/okx-poc-preinstall 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 @yuva2210/okx-poc-preinstall 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. @yuva2210/okx-poc-preinstall on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-10657

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @yuva2210/okx-poc-preinstall-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