Which versions of @yuva2210/poc-depconf are malicious?

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

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

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

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

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

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

Malicious package

@yuva2210/poc-depconfnpm

Advisory published Sep 22, 2026Updated Sep 24, 2026

@yuva2210/poc-depconf is a confirmed malicious npm package (MAL-2026-16532) 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/poc-depconf (npm)

MAL-2026-16532

Immediate action

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

npm uninstall @yuva2210/poc-depconf

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

b21113a6f334babb41a9102ebb839ed13f32df5040a00aaf6bb85815a7586821

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @yuva2210/poc-depconf (2 malicious versions).
If you installed it — respond
Remove @yuva2210/poc-depconf 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/poc-depconf 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/poc-depconf 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-10658

Credits

ReversingLabs · finder

Detect & block this

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