What does the quickwinston malware do?

The OpenSSF Package Analysis project identified 'quickwinston' @ 3.19.3 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of quickwinston are malicious?

The following npm versions of quickwinston are flagged malicious: 3.19.3. Treat any of these as compromised.

How do I remediate quickwinston if I installed it?

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

If quickwinston 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 quickwinston across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for quickwinston (version 3.19.3).

Malicious package

quickwinstonnpm

Advisory published Jun 8, 2026Updated Jun 9, 2026

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

Malicious code in quickwinston (npm)

MAL-2026-5365

Immediate action

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

npm uninstall quickwinston

What this malware does

The OpenSSF Package Analysis project identified 'quickwinston' @ 3.19.3 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

3.19.3

Indicators of compromise (SHA-256)

304b4e430bff604f20121bc97398fa6ee18a25c16187d31b6553248bc54e63c7

Detection & response playbook

Malicious package

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

Credits

OpenSSF: Package Analysis · finder

Detect & block this

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