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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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?

Search your lockfiles and build artifacts for @deadcode09284814/axios-util (2 malicious versions).

Malicious package

@deadcode09284814/axios-utilnpm

Advisory published May 20, 2026Updated May 26, 2026

@deadcode09284814/axios-util is a confirmed malicious npm package (MAL-2026-4379) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @deadcode09284814/axios-util (npm)

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
Search your lockfiles and build artifacts for @deadcode09284814/axios-util (2 malicious versions).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Explore

All malware advisories How O3 detects malware Vulnerability database