Which versions of qweqweqwexxx are malicious?

The following npm versions of qweqweqwexxx are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate qweqweqwexxx if I installed it?

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

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

Yes — qweqweqwexxx is associated with the GHSA-wc72-9fj6-c8hq, RLMA-2025-05495, RLUA-2025-05921 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 qweqweqwexxx 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 qweqweqwexxx (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging qweqweqwexxx across your stack and pipelines.

Malicious package

qweqweqwexxxnpm

qweqweqwexxx is a confirmed malicious npm package (MAL-2025-47960) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in qweqweqwexxx (npm)

MAL-2025-47960

Immediate action

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

npm uninstall qweqweqwexxx

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.0

Indicators of compromise (SHA-256)

8eb4579b71df57bf70c32bdf8375874927db8256e0dbeb573b748d12439bbe26

c9418151955d5a64fc7dd3b9d892d4f5e6ea885ba6d6ad553c4ba211731be74f

f5615ec0faee07eebde8a4dc8f0e8e545289149ba19f81af7f2a3d7dc4df6638

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 qweqweqwexxx (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging qweqweqwexxx across your stack and pipelines.
If you installed it — respond
Remove qweqweqwexxx 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 qweqweqwexxx 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 qweqweqwexxx 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. qweqweqwexxx on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wc72-9fj6-c8hqRLMA-2025-05495RLUA-2025-05921

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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