Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update rspack monorepo to v1.1.8 (main) #1240

Merged
merged 1 commit into from
Dec 19, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 19, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@rspack/cli (source) 1.1.6 -> 1.1.8 age adoption passing confidence
@rspack/core (source) 1.1.6 -> 1.1.8 age adoption passing confidence

Release Notes

web-infra-dev/rspack (@​rspack/cli)

v1.1.8

Security Vulnerability Report

Overview

This is a re-release version of 1.1.6

On 12/19/2024, 02:01 (UTC), we discovered that our npm packages @rspack/core and @rspack/cli were maliciously attacked. The attacker released v1.1.7 using a compromised npm token, which contained malicious code. We took immediate action upon discovering the issue.

Impact

  • Affected versions: @rspack/core and @rspack/cli v1.1.7
  • Duration: 12/19/2024, 02:01 (UTC), lasting approximately 1 hour
  • Malicious code impact: After npm install, the postinstall script in package.json runs malicious code in dist/util/support.js. We are currently analyzing the full impact of malicious code.

Actions Taken

Upon discovery, we immediately deprecated the affected v1.1.7, redirected the npm latest tag to v1.1.6, and reset all related tokens.
Subsequently, we released a secure new version v1.1.8.

Recommended Actions

If you installed v1.1.7 during the affected period, please:

  1. Update to the latest safe version immediately: @rspack/core and @rspack/cli to >= 1.1.8
  2. Check your system for any unusual activity

Apology and Commitment

We deeply apologize for the risks caused by this incident. To prevent similar incidents from happening again, we will implement stricter token management protocols and enhance our security review processes.
If you have any questions or discover any suspicious activity, please create an issue or send an email to: [email protected]
We will continue to follow and respond to community feedback.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title chore(deps): update dependency @rspack/cli to v1.1.7 (main) chore(deps): update dependency @rspack/cli to v1.1.7 (main) - autoclosed Dec 19, 2024
@renovate renovate bot closed this Dec 19, 2024
@renovate renovate bot deleted the renovate/main-rspack-monorepo branch December 19, 2024 06:12
@renovate renovate bot changed the title chore(deps): update dependency @rspack/cli to v1.1.7 (main) - autoclosed chore(deps): update dependency @rspack/cli to v1.1.7 (main) Dec 19, 2024
@renovate renovate bot reopened this Dec 19, 2024
@renovate renovate bot force-pushed the renovate/main-rspack-monorepo branch from 07eb650 to d39b2d7 Compare December 19, 2024 12:20
@renovate renovate bot changed the title chore(deps): update dependency @rspack/cli to v1.1.7 (main) chore(deps): update rspack monorepo to v1.1.8 (main) Dec 19, 2024
@renovate renovate bot force-pushed the renovate/main-rspack-monorepo branch from d39b2d7 to 2d4b948 Compare December 19, 2024 15:44
@Robot-Inventor Robot-Inventor merged commit 11a9032 into main Dec 19, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant