Which versions of @qwedqwed/axios are malicious?

The following npm versions of @qwedqwed/axios are flagged malicious: 1.16.2, 1.16.6, 1.16.12. Treat any of these as compromised.

How do I remediate @qwedqwed/axios if I installed it?

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

I already installed @qwedqwed/axios — how do I know if it already compromised me?

If @qwedqwed/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 @qwedqwed/axios part of a known attack campaign?

Yes — @qwedqwed/axios is associated with the IN-MAL-2026-003478, IN-MAL-2026-007422, IN-MAL-2026-007421 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 @qwedqwed/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 @qwedqwed/axios (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @qwedqwed/axios across your stack and pipelines.

Malicious package

@qwedqwed/axiosnpm

Malicious code in @qwedqwed/axios (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4422

Immediate action

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

npm uninstall @qwedqwed/axios

What this malware does

Package @qwedqwed/axios is published under a scope that does not belong to the real axios maintainers but copies axios's README, source, homepage (axios-http.com), repository (github.com/axios/axios), and author metadata (Matt Zabriskie) verbatim to present itself as the genuine axios library. Its package.json declares two runtime dependencies that the real axios does not use: @caspianph/storyteller@^1.1.12 and math@^0.0.3. The math name is a long-abandoned npm utility frequently abused as a dependency-confusion / typosquat target, and @caspianph/storyteller is an unknown package under an unrelated scope. Installing or requiring @qwedqwed/axios resolves and loads both of those packages into the installer's dependency graph. The axios source bytes shipped in this tarball are themselves benign (the ping strings flagged are inside axios's normal HTTP adapter / utility code, not an exfil path), but the package functions as a lure: the harmful surface is the silently-pulled transitive code, not this tarball's own JavaScript.

Malicious versions

3 flagged

1.16.21.16.61.16.12

Indicators of compromise (SHA-256)

119efce3cb464ef8c7b605ec49768619ac9ef49b9981d4b0a530ff1829194b8c

f5a151202e60ecc066a36811f1cc7cec2c97d4af22bc47fee74da0ebf106e4de

65cc6ad7f5d72e7e50a4493915cc5b8ce23b39b6f25ca5515228be44695016ca

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 @qwedqwed/axios (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @qwedqwed/axios across your stack and pipelines.
If you installed it — respond
@qwedqwed/axios is a typosquat — you almost certainly intended a legitimately-named package. Remove @qwedqwed/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 @qwedqwed/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 @qwedqwed/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. @qwedqwed/axios on npm has been identified as a malicious package (versions 1.16.2, 1.16.6, 1.16.12 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003478IN-MAL-2026-007422IN-MAL-2026-007421

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @qwedqwed/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