MAL-2026-20265: Malicious code in jmrwd-gjdob-util (npm)

Published Nov 20, 2026
·
Updated

--- -= Per source details. Do not edit below this line.=-

Source: amazon-inspector (07f940c4e474df4e519fef56fb93112839d41ea5c2ca9c28a32cbed6195c3d25) On require of this package, index.js reads a numeric byte array from a non-standard b field inside package.json, XORs each byte with 0x96, and stashes the resulting string on globalThis. lib/runner.js then compiles and runs that string via Function('require','dirname', <decoded>)(require, dirname). The decoded payload in this version is a console.log(1) stub, but the mechanism is a generic staged loader: the manifest carries the actual JavaScript source as encoded data, hidden from normal inspection, and any republished version can swap in arbitrary code without touching the shipped JS. The package has an empty exports object, an empty README, and a random-looking name, so it provides no library functionality — the only effect of loading it is to execute attacker-controlled code reconstructed from a concealed manifest field. This is the characteristic shape of a staged npm dropper shell.

Source: ghsa-malware (9948c5afdd593448c2e7b97b8eb54131b3d82374a47e099c12394b0878828539) 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.

Affected Software

1 affected component
npm/jmrwd-gjdob-util*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove npm/jmrwd-gjdob-util from your environment.

    Remove the jmrwd-gjdob-util package; removing it may not remove other malicious software resulting from its installation.

  2. Operational

    Rotate all secrets and keys stored on the affected computer immediately, using a different computer.

Event History

Nov 20, 2026
Advisory Published
via OSV·01:02 AM
Data Sourced
via OSV·01:02 AM
DescriptionAffected Software

Frequently Asked Questions

1

What action triggers execution of the concealed code?

Execution is triggered when the package is loaded with require. Its index.js decodes data from the package.json _b field and lib/runner.js executes the decoded string using Function.

2

What does the decoded payload do in the analyzed version?

The decoded payload is a console.log(1) stub in the analyzed version. However, the package structure is a staged loader, so a republished version could place different JavaScript in the encoded manifest field without changing the shipped JavaScript files.

3

How can I identify the suspicious execution mechanism in an installed copy?

Inspect the package.json file for a non-standard numeric _b field, then examine whether index.js XOR-decodes it with 0x96 and whether lib/runner.js passes the result to Function with require and __dirname. The package also has an empty exports object and empty README.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203