Which versions of aftermath-sui are malicious?

The following npm versions of aftermath-sui are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate aftermath-sui if I installed it?

aftermath-sui 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 aftermath-sui — how do I know if it already compromised me?

If aftermath-sui 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 aftermath-sui part of a known attack campaign?

Yes — aftermath-sui is associated with the IN-MAL-2026-010941 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 aftermath-sui 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 aftermath-sui (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aftermath-sui across your stack and pipelines.

Malicious package

aftermath-suinpm

aftermath-sui is a confirmed malicious npm package (MAL-2026-10942) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aftermath-sui (npm)

MAL-2026-10942

Immediate action

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

npm uninstall aftermath-sui

What this malware does

The aftermath-sui package was published to the npm registry by user 'jet0010001' (maintainer email [email protected]) as part of a dependency-confusion / reconnaissance campaign impersonating the Aftermath Finance SDK (Aftermath Finance is a DeFi protocol on the Sui blockchain). The package was published at version 99.0.0 - an inflated version number characteristic of dependency-confusion attacks, intended to cause a misconfigured resolver to prefer this public lookalike over the intended private/internal dependency of the same name.

The package declares a preinstall hook ("node setup.js || true") that executes automatically at npm install time, before any application code runs. The bundled setup.js performs host reconnaissance and credential harvesting: it collects the machine hostname, the current OS username, the current working directory, the contents of /etc/hostname, and the output of 'git remote -v', and it enumerates process environment variables whose names match the pattern /key|secret|token|pass|auth|private|drone|gitea|sui|admin|deploy/i - capturing API keys, secrets, tokens, passwords, and Sui/deploy/CI credentials. The collected data is serialized to JSON and exfiltrated via an HTTPS POST to the hardcoded attacker-controlled endpoint https://2.25.140.71:8443/aftermath/npm-dep-conf, with TLS certificate verification disabled (rejectUnauthorized: false) so a self-signed listener is accepted. Errors are silently swallowed so the install appears to succeed. The published module code (index.js) is a benign stub exporting only { version: "99.0.0" }, consistent with a package built solely to deliver the install-time beacon.

The install-time payload is byte-for-byte identical across the campaign's packages (aftermath-finance, aftermath-sui, aftermathfi), all published by the same maintainer within seconds of each other and all beaconing to the same collector.

The package's preinstall script (setup.js, invoked via scripts.preinstall = 'node setup.js') runs automatically on npm install. It enumerates process.env and filters keys matching /key|secret|token|pass|auth|private|drone|gitea|sui|admin|deploy/i, and additionally collects os.hostname(), os.userInfo().username, process.cwd(), the contents of /etc/hostname, and the output of git remote -v. The collected JSON is POSTed to a hardcoded bare-IP endpoint at https://2.25.140.71:8443/aftermath/npm-dep-conf with TLS certificate verification disabled (rejectUnauthorized:false). The destination is a raw IP unrelated to any legitimate Aftermath Finance / Sui infrastructure, and the package name resembles the Aftermath Finance ecosystem, consistent with a typosquat targeting Sui/Aftermath developers.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

0157a24eb15337a04879abcb94a3293e67dc6cea5efce56541aaa7a43ab5cd53

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 aftermath-sui (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aftermath-sui across your stack and pipelines.
If you installed it — respond
aftermath-sui 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 aftermath-sui 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 aftermath-sui 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. aftermath-sui on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010941

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks aftermath-sui-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