@htooayelwinict/travis234 has no safe version.

HighAdvisory sweepnpm

The advisories that named @htooayelwinict/travis234 on the npm registry did not list releases, because it never had a legitimate one. There is no version to upgrade to: remove it outright. It is named in 1 incident we track. @htooayelwinict/travis234 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

None

Safe versionsRemove it, do not upgrade

No release of this package is known good. If it is in your tree, treat the machine as compromised, not just out of date.

Ecosystem: npm
Worst severity: High
Incidents: 1
First flagged: 9 Nov 2026
Type: Advisory sweep

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

Version data

No release is known good. There is no version list because there is no safe version.

Check what you actually have installed with npm ls @htooayelwinict/travis234.

The source advisories flagged the package itself rather than particular releases. Treat any resolved version as malicious and remove the dependency; there is nothing to upgrade to.

The incident

The incident that flagged it

HighAdvisory sweep9 Nov 2026

GitHub Advisory malware sweep, 9 November 2026

19 packages from GitHub malware advisories published 8–9 November 2026 (after the previous sweep cutoff). Headlines: PyPI chromacli infostealer campaign, RubyGems oastify.com pentest beacons, PyPI infostealer droppers, and dependency-confusion probes.

Versions named here: *Read 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.
Remove the dependency: no release is known good, so there is nothing to pin to. 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 @htooayelwinict/travis234 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