grafeno-billing has 1 compromised version.

HighAdvisory sweepnpm

grafeno-billing has 1 version on the npm registry flagged in 1 incident we track. Only the exact versions listed below were named by the source advisories. grafeno-billing was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.

Check my package-lock.json What to do

At a glancenpm

Compromised versionDo not install these

If one is in your tree, treat the machine as compromised, not just out of date.

Ecosystem: npm
Worst severity: High
Incidents: 1
First flagged: 30 Aug 2026
Type: Advisory sweep

Version data comes from the public advisories cited on each incident page.

Affected versions

The exact releases to look for.

Check what you actually have installed with npm ls grafeno-billing.

grafeno-billing@1.0.0

The incident

The incident that flagged it

HighAdvisory sweep30 Aug 2026

GitHub Advisory malware sweep, 30 August 2026

Second wave of the grafeno-* Brazilian-fintech-themed cluster surfaced on 2026-08-30: grafeno-webhook, grafeno-payments, and grafeno-billing (all v1.0.0) reuse the 216.126.236.46 C2 host from Wave 1 but swap the x.sh + crontab mechanism for env-var scraping (AWS|TOKEN|KEY|SECRET|PASS|API) + a reverse bash shell on port 4444. Plus three CWE-506 boilerplate takedowns: quesoeducation, opiumbest, gclassroom.

Versions named here: 1.0.0Read the incident →

What to do

Installed one of these? Start here.

Treat the machine as compromisedUpgrading is not enough. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

Rotate every credential that machine or CI job could reach, such as registry tokens, cloud keys, SSH keys and CI secrets, from a different machine.
Pin to a version not listed above, then reinstall from a clean lockfile.
Clear caches and private mirrors. Artifactory, Nexus, Verdaccio and devpi routinely keep serving a tarball after the public registry has pulled it.
Read the incident write-up. Recommended actions differ per incident, and some have specific indicators of compromise worth searching your logs for.

Same campaign

Other packages in the same incident

If grafeno-billing is in your tree, these are worth checking too. They were published by the same campaign.

See the full incident →All flagged npm packages →

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name and do not infer additional ones. Think this is wrong or incomplete? Tell us.

Check your whole project

Check every dependency, not just this one.

It is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once. It runs in your browser and nothing is uploaded.

Check my package-lock.json All npm packages