Which versions of asavie-ui are malicious?

The following npm versions of asavie-ui are flagged malicious: 99.0.2. Treat any of these as compromised.

How do I remediate asavie-ui if I installed it?

asavie-ui establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed asavie-ui — how do I know if it already compromised me?

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

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

Malicious package

asavie-uinpm

Malicious code in asavie-ui (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4268

Immediate action

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

npm uninstall asavie-ui

What this malware does

callback.js collects host identity information (os.hostname(), os.userInfo()) and transmits it via https.get() to an external endpoint at install/load time. The combination of OS-level identity collection followed by outbound HTTPS in a callback script is consistent with installer reconnaissance/beaconing. The package name and structure (a 99.x.x version of a generic UI-named package) further suggests a non-legitimate publication. No corresponding legitimate functionality (no UI code, no documented purpose) accompanies the data-collection routine.

The OpenSSF Package Analysis project identified 'asavie-ui' @ 99.0.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.0.2

Indicators of compromise (SHA-256)

b0478f8efd496e7baa22fc9623c2a786f95453a6ad1f0230d8d4eeca0b12f17f

3f6ffe8a3c127532ed603e45f0fe214faa8595fef46edb0a3f7ddb4efe468984

bf12a913426dee622d500474fe3629c5bb3246e1793e3f210916885c6d0481a9

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for asavie-ui (version 99.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging asavie-ui across your stack and pipelines.
If you installed it — respond
asavie-ui establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If asavie-ui 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 asavie-ui 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. asavie-ui on npm has been identified as a malicious package (version 99.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004353IN-MAL-2026-004352

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks asavie-ui-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring