MAL-2026-16304 Malicious code in @nimbusedge2/authxsas1 (npm)
Malicious package
Published
MAL-2026-16304 is a malicious package: @nimbusedge2/authxsas1 (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-16304/ (Markdown: https://insights.sbomify.com/MAL-2026-16304/index.md)
- Package
- @nimbusedge2/authxsas1
- Registry
- npm
What is MAL-2026-16304?
MAL-2026-16304 is a malicious package in @nimbusedge2/authxsas1, published on 21 Sep 2026.
Official description
package.json declares a preinstall lifecycle script that runs automatically on
npm install. The script uses curl to fetch the cloud instance metadata service (169.254.169.254, accessed via the nip.io wildcard-DNS wrapper 169.254.169.254.nip.io/latest/meta-data/), base64-encodes the response, and POSTs it to a hardcoded third-party endpoint at http://canarytokens.com/terms/7dc94zmd3so67n5vbz5bxmt7v/contact.php. On cloud and CI installers this discloses instance identity metadata and, where IMDSv1 is reachable, temporary IAM credentials to the destination. The package's description field self-labels the beacon as an 'Authorized report' with a wearehackerone.com contact address; that label is author-controlled and does not change the behavior class — installing the package causes installer-side host and cloud metadata to be sent off-host to a canarytoken beacon.What should I do about MAL-2026-16304?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.