Which versions of vitest-axios are malicious?

The following npm versions of vitest-axios are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate vitest-axios if I installed it?

vitest-axios is a typosquat — you almost certainly intended a legitimately-named package. Remove vitest-axios, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed vitest-axios — how do I know if it already compromised me?

If vitest-axios was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is vitest-axios part of a known attack campaign?

Yes — vitest-axios is associated with the GHSA-6v5g-7h35-h33q, IN-MAL-2026-011335 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find vitest-axios across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vitest-axios (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vitest-axios across your stack and pipelines.

Malicious package

vitest-axiosnpm

vitest-axios is a confirmed malicious npm package (MAL-2026-11030) that typosquats a legitimate package to trick installs (malicious version 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vitest-axios (npm)

MAL-2026-11030

Immediate action

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

npm uninstall vitest-axios

What this malware does

Package published as vitest-axios re-ships axios source, README, homepage, and repository metadata to impersonate the legitimate axios HTTP client. In dist/node/axios.cjs (the declared main), a top-level var fs = require('fs-extra-core'); replaces upstream axios's require('fs'), and fs-extra-core@^1.3.4 is declared in dependencies — a lookalike of the legitimate fs-extra package. Because the require sits at the top of the main module, whatever fs-extra-core exports or executes runs on every require('vitest-axios') / import 'vitest-axios', resolving attacker-controlled code into the installer's dependency tree at import time. Package metadata (name, description, keywords, repository axios/axios, homepage axios-http.com, README titled axios-native, copyright dated 2026) is engineered to deceive installers into believing they are installing axios or a vitest-axios integration.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

5309dc413289d10c8d1cf1b2593f5e29c7810c23f60cb8e2c7709884cdba4c04

3e61d93e82877f836aaba3dd528e79f3e5f4b1bd12ce64b40202bbecd08a2747

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vitest-axios (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vitest-axios across your stack and pipelines.
If you installed it — respond
vitest-axios is a typosquat — you almost certainly intended a legitimately-named package. Remove vitest-axios, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If vitest-axios was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks vitest-axios before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. vitest-axios on npm has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6v5g-7h35-h33qIN-MAL-2026-011335

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vitest-axios-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