Which versions of @aonunited/angular are malicious?

The following npm versions of @aonunited/angular are flagged malicious: 99.0.0, 99.0.1. Treat any of these as compromised.

How do I remediate @aonunited/angular if I installed it?

@aonunited/angular 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 @aonunited/angular — how do I know if it already compromised me?

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

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

Malicious package

@aonunited/angularnpm

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

MAL-2026-5150

Immediate action

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

npm uninstall @aonunited/angular

What this malware does

On npm install, the package's preinstall script (preinstall.js) collects the installer's hostname, OS username, current working directory, and a timestamp, then sends them to two attacker-style out-of-band endpoints: a DNS lookup of a subdomain under oast.fun (an Interactsh-style callback service) constructed from the installer's identifiers, and an HTTPS POST of a JSON payload to a webhook.site URL. The package itself provides no functionality — it is a high-version (99.0.1) namespace-confusion lure against an internal @aonunited/angular package, designed so that any environment whose resolver picks the public registry copy will auto-execute the beacon. Although the metadata describes this as authorized HackerOne VDP research, the package is published to the public npm registry, so any developer or build system that installs or mistypes it leaks host fingerprints to third-party infrastructure without consent.

The OpenSSF Package Analysis project identified '@aonunited/angular' @ 99.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

99.0.099.0.1

Indicators of compromise (SHA-256)

411e19a999b3354e6b5ad40e6da82882c1bf314a35d722ade7b3e23eb9c4a46c

63dac830216ae445ebe7c5f45534e479d73a23a098ea9fc5740eeded5ebab4c9

99c3d41b561dd83a12c6cfe9ea516a785019ca83f967e8082dd1d0846fd87aaf

876080f93d0095e9fa2ea21979aa3c193f06f2dbbc5214aa9bcc8451865f3100

ef384053c91cc48a45d530e3a54f9b627a2e52c159c0866aaacb018f92090783

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

Campaign

IN-MAL-2026-005103IN-MAL-2026-005104IN-MAL-2026-005163IN-MAL-2026-005162

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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