All @onerjs/addons versions

@onerjs/addons @8.52.3

rejected
This version was rejected. It did not pass GreenFlagged's security review and is not served by the registry. The findings and risk dispositions below explain why.
49
Risk Score
Apache-2.0
License
No
Install Scripts
0
Dependencies
3
Dev Dependencies
253.2 KB
Package Size
Published

Maintainers

richard_lin

Keywords

3Djavascripthtml5webglbabylon.js

Dev Dependencies (3)

PackageConstraintRegistry Status
@dev/addons ^1.0.0 Not imported
@onerjs/core 8.52.3 auto_approved
@dev/build-tools ^1.0.0 Not imported

Changes from v8.52.2

No metadata changes detected.

File Changes

0 added 0 removed 1 modified size delta: .0 KB

SAST Findings (2)

CRITICAL MAL-2026-4410: Malicious code in @onerjs/addons (npm) osv

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (a7d3b8a435a56ca78d7a2f4ca7077b8a96f968d29e32dd01580fdf01cee442f5) Package is published as `@onerjs/addons` but ships a verbatim copy of `@babylonjs/addons` source while declaring Babylon.js identity in its metadata: `package.json` sets `homepage` to `https://www.babylonjs.com` and `repository.url` to `https://github.com/BabylonJS/Babylon.js.git`, and the README is titled `# Babylon.js Addons`. Every internal import of `@babylonjs/core` has been rewritten to `@onerjs/core` (e.g., `atmosphere/atmosphere.js` line 6: `import { Color3 } from "@onerjs/core/Maths/math.color.js";`), and `peerDependencies` declares `"@onerjs/core": "^8.0.0"`. The `@onerjs` scope is unrelated to Babylon.js or Microsoft. Installers who believe they are pulling Babylon.js addons will additionally install `@onerjs/core` from the same unrelated publisher, who can ship arbitrary code under the guise of Babylon.js core at any future version within the `^8.0.0` range. The lure package itself contains no lifecycle hooks or in-package exfil, but the structural design — identity impersonation plus a peerDependency redirect to a sibling package controlled by the same publisher — is namespace-abuse: the harm arrives through the rerouted dependency.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

Review Summary

Risk score: 49. Findings: 1 critical (+40), 3 low (+9), 1 info (+0).

Commit: 0070197f35a0 Browse source

Published to npm: