NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

hexo-commitlint-config-angular-nuxtjs-neptunenpm

Advisory published Updated

hexo-commitlint-config-angular-nuxtjs-neptune is a confirmed malicious npm package (MAL-2025-187351) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hexo-commitlint-config-angular-nuxtjs-neptune (npm)

MAL-2025-187351
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall hexo-commitlint-config-angular-nuxtjs-neptune

What this malware does

This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and publish derivative packages with randomized names to inflate developer reputation scores for tea protocol token rewards. The malicious payload modifies package.json to remove private flags, changes version numbers, generates random Indonesian-themed package names (some variants are also in English), and continuously republishes variants to pollute the npm registry.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

aa04a244c2369734edc8b55f4a7af30007d71d3275a23f60c9548644507fb197

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for hexo-commitlint-config-angular-nuxtjs-neptune (all published versions).

  2. If you installed it — respond

    Remove hexo-commitlint-config-angular-nuxtjs-neptune from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If hexo-commitlint-config-angular-nuxtjs-neptune 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

No. hexo-commitlint-config-angular-nuxtjs-neptune on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks hexo-commitlint-config-angular-nuxtjs-neptune-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
hexo-commitlint-config-angular-nuxtjs-neptune (npm) malicious package — MAL-2025-187351 | O3 Security