Skip to main content
MalwarePublished Updated

jshelperdependenceny (npm) · Malicious Code

Affects jshelperdependencenySource GCVE Database

0

Malicious package : remove jshelperdependenceny and rotate any secrets on hosts that installed it.

Data as of 26 Oct 2026, 17:57 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-18288

What to do

Remove jshelperdependenceny from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

ProductAffectedFixed in
npmjshelperdependencenyAffected
  • =99.0.0
  • =1.0.0
  • =0.0.0-stage
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (dc4d19697f4104351bb25b7e568018ec6ed85d626b7265fb4b9682ae12183be9) npm package 'jshelperdependenceny' is published at version 99.0.0 with a preinstall banner stating it is intended to shadow an internal v1.0.0 package of the same name — the classic dependency-confusion shape of using an inflated version to win resolution against a private registry. On install, package.json runs 'node preinstall.js || true', which collects os.hostname(), os.platform(), os.arch(), and the package name/version and POSTs them as JSON to a URL taken from the DC_CALLBACK_URL environment variable, defaulting to http://127.0.0.1:5656/exfil. The env-var override turns the loopback default into a functional attacker-configurable beacon that fires automatically on npm install and discloses installer host identifiers plus confirmation that the shadowed internal name resolved to this public artifact. ## Source: ghsa-malware (f3ef4f78032c4c500bebdc4417e95c83512df2ff69219e835ecfd697274c1657) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

References

Community reviews

Loading reviews…