Which versions of @zhiend989/asdfqwer are malicious?

The following npm versions of @zhiend989/asdfqwer are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate @zhiend989/asdfqwer if I installed it?

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

If @zhiend989/asdfqwer 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 @zhiend989/asdfqwer part of a known attack campaign?

Yes — @zhiend989/asdfqwer is associated with the RLMA-2024-06092, RLUA-2026-10661 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 @zhiend989/asdfqwer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @zhiend989/asdfqwer (version 2.0.0).

Malicious package

@zhiend989/asdfqwernpm

Advisory published Oct 16, 2024Updated Sep 24, 2026

@zhiend989/asdfqwer is a confirmed malicious npm package (MAL-2024-9489) that executes malicious code on install (malicious version 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zhiend989/asdfqwer (npm)

MAL-2024-9489

Immediate action

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

npm uninstall @zhiend989/asdfqwer

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

45a38617b25f7151b167a060e2db495850aee8756bb3a3a79c6fd9f86586eb28

89aa8122053f122da043d870d738397736c38d08c29e2bda9dc6f3de1e4d9089

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @zhiend989/asdfqwer (version 2.0.0).
If you installed it — respond
Remove @zhiend989/asdfqwer 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 @zhiend989/asdfqwer 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. @zhiend989/asdfqwer on npm has been identified as a malicious package (version 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-06092RLUA-2026-10661

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @zhiend989/asdfqwer-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