@aonunited/angularnpm
Advisory published Updated
@aonunited/angular is a confirmed malicious npm package (MAL-2026-5150) that opens a backdoor for remote access (malicious versions 99.0.0, 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @aonunited/angular (npm)
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.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for @aonunited/angular (2 malicious versions).
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 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
Campaign
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.