Which versions of asdsafsadad are malicious?

The following npm versions of asdsafsadad are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate asdsafsadad if I installed it?

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

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

Yes — asdsafsadad is associated with the GHSA-7j38-gr5c-v4mv, RLMA-2026-06070, RLUA-2026-10692 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 asdsafsadad across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for asdsafsadad (version 1.0.1).

Malicious package

asdsafsadadnpm

Advisory published Jul 31, 2026Updated Sep 24, 2026

asdsafsadad is a confirmed malicious npm package (MAL-2026-11241) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in asdsafsadad (npm)

MAL-2026-11241

Immediate action

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

npm uninstall asdsafsadad

What this malware does

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

1 flagged

1.0.1

Indicators of compromise (SHA-256)

67f3884787706e55b04fcf9ab0749dd3f91bd1f8a9d06bd86180483dd9f581cc

093a35218da40085f9abbc7e3541b1daa33aae640ad755ba058088d15e478055

636fbaff927a947762d26eddeb6304f020e17a87eec1057db47b624e893b665e

Detection & response playbook

Malicious package

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

Campaign

GHSA-7j38-gr5c-v4mvRLMA-2026-06070RLUA-2026-10692

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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