npm package report

Is onfire.js safe?

Versions 2.1.1 and 2.2.1 of onfire.js were compromised (maintainer account compromise). Other versions are not flagged as malicious.

Do not install onfire.js 2.1.1 or 2.2.1

CRITICALanalyst verified

Maintainer account compromise, part of the mini_shai_hulud_antv_2026_05_19 campaign. Added to CyberXYZ 2026-05-19, verified by a CyberXYZ analyst.

// what we observed

atool npm account compromise (i@hust.cc / hustcc on GitHub). Same actor compromised AntV namespace. Published two waves of malicious versions across 24 packages; all versions from this account are suspect until token rotation confirmed.

// versions and what to do

Malicious: 2.1.1, 2.2.1
Move to: 2.0.1 newest 2.x release, no known advisory

If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.

npm install onfire.js@2.0.1

// reach

0 direct dependencies

none carry a known advisory

0 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-10-31 at 00:03 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.