Skip to content

chore(ci): add deprecate action;#10591

Merged
DigitalBrainJS merged 1 commit intoaxios:v1.xfrom
DigitalBrainJS:chore/ci-deprecate
Mar 31, 2026
Merged

chore(ci): add deprecate action;#10591
DigitalBrainJS merged 1 commit intoaxios:v1.xfrom
DigitalBrainJS:chore/ci-deprecate

Conversation

@DigitalBrainJS
Copy link
Copy Markdown
Collaborator

No description provided.

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 1 file

Confidence score: 2/5

  • There is a high-confidence security risk in .github/workflows/deprecate.yml: workflow_dispatch input is interpolated directly into a run shell command, which can enable command injection.
  • Because this issue is severity 8/10 with clear user-controlled input reaching shell execution, it is a strong merge risk and should be fixed before merging.
  • Pay close attention to .github/workflows/deprecate.yml - sanitize/validate dispatch inputs and pass them through environment variables instead of direct shell interpolation.
Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".github/workflows/deprecate.yml">

<violation number="1" location=".github/workflows/deprecate.yml:28">
P1: Do not interpolate `workflow_dispatch` input directly into a `run` shell command; validate and pass it via environment variables first to prevent command injection.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

- name: Deprecate selected version
run: |
echo "Deprecating axios@${{ github.event.inputs.version }}"
npm deprecate axios@${{ github.event.inputs.version }} "🚨 SECURITY: compromised dependency (plain-crypto-js). DO NOT USE. Downgrade to 1.13.6"
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai bot Mar 31, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: Do not interpolate workflow_dispatch input directly into a run shell command; validate and pass it via environment variables first to prevent command injection.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/deprecate.yml, line 28:

<comment>Do not interpolate `workflow_dispatch` input directly into a `run` shell command; validate and pass it via environment variables first to prevent command injection.</comment>

<file context>
@@ -0,0 +1,30 @@
+      - name: Deprecate selected version
+        run: |
+          echo "Deprecating axios@${{ github.event.inputs.version }}"
+          npm deprecate axios@${{ github.event.inputs.version }} "🚨 SECURITY: compromised dependency (plain-crypto-js). DO NOT USE. Downgrade to 1.13.6"
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
</file context>
Fix with Cubic

@DigitalBrainJS DigitalBrainJS merged commit e2bed7f into axios:v1.x Mar 31, 2026
17 checks passed
@codythatsme
Copy link
Copy Markdown

@DigitalBrainJS The issue calling out this compromised version was deleted. Was this intentional?

@haoqunjiang
Copy link
Copy Markdown

Why does it recommend 1.13.6 instead of 1.14.0?

@jasonsaayman
Copy link
Copy Markdown
Member

@codythatsme no it was not

@codythatsme
Copy link
Copy Markdown

@codythatsme no it was not

Yes, it was. https://github.com/axios/axios/issues/10590

There were at least 3 other issues that got deleted after this one. Good to see the current one stay up though. Good luck getting everything contained ❤️

@jasonsaayman
Copy link
Copy Markdown
Member

thanks i meant it was not actively me, ie attacker did this

shaanmajid added a commit to shaanmajid/axios that referenced this pull request Mar 31, 2026
jasonsaayman pushed a commit that referenced this pull request Apr 1, 2026
@DigitalBrainJS
Copy link
Copy Markdown
Collaborator Author

@haoqunjiang It was the middle of the night when I was alerted to issue #10590 with the word "malicious." While I was waking up and trying to figure out what was going on, version 1.13.6 was the last one I'd checked days before, and I thought it was a safe point. The attack vectors weren't clear at the time I created the PR, and it wasn't clear whether 1.14.0 was infected. Since I had no direct access to the npm account, the PR was a desperate attempt to slow the attack until npm administration could come to the rescue.

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.

4 participants