npm

The @onescience/onecode npm Malware Advisory

Updated 18 Nov 2026 · Incident date 16 Jul 2026

GitHub and OpenSSF mark @onescience/onecode on npm as malware, and Amazon Inspector reports that its install script fetched and set up an unverified program.

npm replaced @onescience/onecode with a security holding package on 18 November 2026. The same day, GitHub published malware advisory GHSA-w94w-q524-wgvr for every version.

What happened

Amazon Inspector reports that the npm postinstall hook fetched and set up a program from a hardcoded IP address.

  • The hook calls ensurePlatformBinary(), which downloads a .tgz archive from 218.90.133.98 on port 4443.
  • The request sets rejectUnauthorized: false, which turns off TLS certificate checks.
  • The hook does no hash or signature check on the download.
  • The hook extracts the archive and links the program to bin/.onecode. The package launcher then runs it.
  • Amazon Inspector says the name and the launcher copy the unrelated opencode project.

Amazon Inspector published its record on 16 July 2026. The code was unavailable for inspection, and no source describes what the downloaded program does.

Affected versions

  • GitHub: all versions (>= 0), with no patched version.
  • OpenSSF MAL-2026-10717: 54 builds of 1.14.50, published from 16 July to 7 August 2026. The first is 1.14.50-202607161038.
  • npm registry: releases ran from 1.14.50-202606300908 (30 June 2026) to 1.19.3-202611031647 (3 November 2026).
  • npm no longer serves these releases. The only versions left are 0.0.0-stage and 0.0.1-security.

Indicators of compromise

  • Download host: 218.90.133.98 on port 4443
  • Download path: /onecode_tgz/onecode-<ver>/onecode-linux-x64-<ver>.tgz
  • Program link: bin/.onecode
  • Evidence file platform-bootstrap.mjs, SHA-256 0795feaceb78b42d123dafb190444f534ea5e51c920775aaafe3ee2cee0acf47
  • Tarball onecode-1.14.50-202607161038.tgz, SHA-1 207b6685273c80f29e0bccca3875606db194ecb7

How to check

List the installed copies in each project.

npm ls @onescience/onecode

List the global installs on the computer.

npm ls -g @onescience/onecode

What to do now

  1. If a command lists the package, run npm uninstall @onescience/onecode. For a global copy, add -g.
  2. Treat that computer as fully compromised, as GitHub advises.
  3. From a different computer, rotate every secret and key stored on the affected computer.
  4. Do not rely on removal alone. GitHub says removal does not guarantee that all malicious software is gone.

What Vigilance would show

These examples show an install hold and the corresponding owner report.

Example install message

Vigilance blocked `@onescience/onecode` 1.14.50-202607161038. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

@onescience/onecode 1.14.50-202607161038

When installed, it downloaded a program from a bare IP address with no security checks and set it up for its launcher to run.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

Is @onescience/onecode malware?

GitHub advisory GHSA-w94w-q524-wgvr and OpenSSF record MAL-2026-10717 classify it as malware. npm took the package down on 18 November 2026.

What does the @onescience/onecode install script download?

No source describes the downloaded program. Amazon Inspector reports that the script fetched it from a bare IP address with no hash or signature check.

Sources

  1. github.com/advisories/GHSA-w94w-q524-wgvr
  2. api.osv.dev/v1/vulns/MAL-2026-10717
  3. registry.npmjs.org/@onescience%2fonecode

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · npm supply chain attacks · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library