Which versions of @lbnqduy180500/musical-winner are malicious?

Every published version of @lbnqduy180500/musical-winner on npm is considered malicious. Remove the package entirely.

How do I remediate @lbnqduy180500/musical-winner if I installed it?

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

If @lbnqduy180500/musical-winner 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.

How do I find @lbnqduy180500/musical-winner across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @lbnqduy180500/musical-winner (all published versions).

Part of a larger attack: @lbnqduy180500 published 15 malicious packages. See the full campaign →

Malicious package

@lbnqduy180500/musical-winnernpm

Advisory published Sep 5, 2025Updated Sep 5, 2025

@lbnqduy180500/musical-winner is a confirmed malicious npm package (MAL-2025-42679) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @lbnqduy180500/musical-winner (npm)

MAL-2025-42679

Immediate action

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

npm uninstall @lbnqduy180500/musical-winner

What this malware does

The package @lbnqduy180500/musical-winner was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @lbnqduy180500/musical-winner-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