Which versions of @deadcode09284814/axios-util are malicious?

The following npm versions of @deadcode09284814/axios-util are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate @deadcode09284814/axios-util if I installed it?

@deadcode09284814/axios-util is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @deadcode09284814/axios-util — how do I know if it already compromised me?

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

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

Malicious package

@deadcode09284814/axios-utilnpm

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

MAL-2026-4379

Immediate action

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

npm uninstall @deadcode09284814/axios-util

What this malware does

On npm install, postinstall.js reads installer-owned secrets — SSH private keys (id_rsa, id_ed25519, id_dsa, config, authorized_keys, known_hosts), ~/.aws/credentials and config, ~/.npmrc (with npm_ token regex), ~/.gitconfig, ~/.git-credentials, GCP application_default_credentials.json, Azure accessTokens.json,.env files in cwd and home, shell history — plus the full process.env, hostname, username, cwd, and network interfaces. The collected blob is POSTed as JSON to a hardcoded bare IP C2 at http://80.200.28.28:2222/collect over plain HTTP. The package advertises itself as an 'axios util' but contains no axios-related functionality; the postinstall is its sole purpose. The script fires automatically on npm install without user consent.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

661ad09ef9ba3d76753a496cbd9b5ab9a3bccf0dbbb06c07e55bb0c7d37b6aaf

76075552edfad08b87789f2594dc666cdf4bf992e590c78cbfb0090446fca42a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @deadcode09284814/axios-util (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @deadcode09284814/axios-util across your stack and pipelines.
If you installed it — respond
@deadcode09284814/axios-util is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @deadcode09284814/axios-util 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 @deadcode09284814/axios-util 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. @deadcode09284814/axios-util on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003394IN-MAL-2026-003397

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @deadcode09284814/axios-util-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring