🚨 [security] Update winston 3.2.1 → 3.18.3 (minor)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ winston (3.2.1 → 3.18.3) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ color (indirect, 3.0.0 → 5.0.2) · Repo

Security Advisories 🚨

🚨 color@5.0.1 contains malware after npm account takeover

Impact

On 8 September 2025, the npm publishing account for color was taken over after a phishing attack. Version 5.0.1 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments.

Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt.

The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.

Patches

npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper.

On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This version is functionally identical to the previously known-good version, published as a patch version bump above the compromised version.

Users should update to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch.

Those operating private registries or registry mirrors should purge the offending versions from any caches.

References

• https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised
• https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack
• https://www.ox.security/blog/npm-packages-compromised/

Point of Contact

In the event suspicious behavior is still observed for the package listed in this security advisory after performing all of the above cleaning operations (see Patches above), please reach out via one of the following channels of communication:

• Bluesky, package owner: https://bsky.app/profile/bad-at-computer.bsky.social
• debug repository, tracking issue (applies to all packages affected in the breach): debug-js/debug#1005

Release Notes

5.0.2

More info than we can show here.

5.0.0

More info than we can show here.

4.2.3

More info than we can show here.

4.2.1

More info than we can show here.

4.2.0

More info than we can show here.

4.1.0

More info than we can show here.

4.0.2

More info than we can show here.

4.0.1

More info than we can show here.

4.0.0

More info than we can show here.

3.2.1

More info than we can show here.

3.2.0

More info than we can show here.

3.1.3

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ color-string (indirect, 1.5.3 → 2.1.2) · Repo · Changelog

Security Advisories 🚨

🚨 color-string@2.1.1 contains malware after npm account takeover

Impact

On 8 September 2025, the npm publishing account for color-string was taken over after a phishing attack. Version 2.1.1 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments.

Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt.

The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.

Patches

npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper.

On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This version is functionally identical to the previously known-good version, published as a patch version bump above the compromised version.

Users should update to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch.

Those operating private registries or registry mirrors should purge the offending versions from any caches.

References

• https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised
• https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack
• https://www.ox.security/blog/npm-packages-compromised/

Point of Contact

In the event suspicious behavior is still observed for the package listed in this security advisory after performing all of the above cleaning operations (see Patches above), please reach out via one of the following channels of communication:

• Bluesky, package owner: https://bsky.app/profile/bad-at-computer.bsky.social
• debug repository, tracking issue (applies to all packages affected in the breach): debug-js/debug#1005

🚨 Regular Expression Denial of Service (ReDOS)

In the npm package color-string, there is a ReDos (Regular Expression Denial of Service) vulnerability regarding an exponential time complexity for
linearly increasing input lengths for hwb() color strings.

Strings reaching more than 5000 characters would see several
milliseconds of processing time; strings reaching more than
50,000 characters began seeing 1500ms (1.5s) of processing time.

The cause was due to a the regular expression that parses
hwb() strings - specifically, the hue value - where
the integer portion of the hue value used a 0-or-more quantifier
shortly thereafter followed by a 1-or-more quantifier.

This caused excessive backtracking and a cartesian scan,
resulting in exponential time complexity given a linear
increase in input length.

Release Notes

2.1.2

More info than we can show here.

2.1.0

More info than we can show here.

2.0.1

More info than we can show here.

2.0.0

More info than we can show here.

1.9.0

More info than we can show here.

1.8.2

More info than we can show here.

1.8.1

More info than we can show here.

1.7.4

More info than we can show here.

1.7.1

More info than we can show here.

1.7.0

More info than we can show here.

1.6.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ fecha (indirect, 2.3.3 → 4.2.3) · Repo · Changelog

Release Notes

4.2.3 (from changelog)

More info than we can show here.

4.2.1 (from changelog)

More info than we can show here.

Does any of this look wrong? Please let us know.

↗️ logform (indirect, 2.1.2 → 2.7.0) · Repo · Changelog

Release Notes

2.7.0

More info than we can show here.

2.6.1

More info than we can show here.

2.6.0

More info than we can show here.

2.5.1

More info than we can show here.

2.5.0

More info than we can show here.

2.4.2

More info than we can show here.

2.4.1

More info than we can show here.

2.4.0

More info than we can show here.

2.3.2

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ triple-beam (indirect, 1.3.0 → 1.4.1) · Repo · Changelog

Release Notes

1.4.1

More info than we can show here.

1.4.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ winston-transport (indirect, 4.3.0 → 4.9.0) · Repo · Changelog

Release Notes

4.9.0

More info than we can show here.

4.8.1

More info than we can show here.

4.8.0

More info than we can show here.

4.7.1

More info than we can show here.

4.7.0

More info than we can show here.

4.6.0

More info than we can show here.

4.5.0

More info than we can show here.

4.4.1

More info than we can show here.

4.4.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 @​colors/colors (added, 1.6.0)

🆕 @​dabh/diagnostics (added, 2.0.8)

🆕 @​so-ric/colorspace (added, 1.1.6)

🆕 @​types/triple-beam (added, 1.3.5)

🆕 fn.name (added, 1.1.0)

🆕 safe-stable-stringify (added, 2.5.0)

🗑️ colornames (removed)

🗑️ colors (removed)

🗑️ colorspace (removed)

🗑️ diagnostics (removed)

🗑️ env-variable (removed)

🗑️ fast-safe-stringify (removed)

🗑️ is-arrayish (removed)

🗑️ simple-swizzle (removed)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)