Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

module-relpathnpm

Advisory published Updated

module-relpath is a confirmed malicious npm package (MAL-2026-14561) that executes malicious code on install (malicious versions 1.0.1, 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in module-relpath (npm)

MAL-2026-14561
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall module-relpath

What this malware does

The package presents itself as relative-import-path (README title, homepage and repository URL point at github.com/marko-js/relative-import-path, and the.d.ts documents only relativeImportPath), but the CJS bundle at dist/index.js does not export the documented API. Instead it exports a single undocumented function modshit(moduleName, size) that reads public/logo.png from the current working directory, slices the trailing size bytes off the file, resolves the path ../${moduleName}/public/logo.png relative to its own directory, creates parent directories as needed, and writes those trailing bytes to that location. The effect is a steganographic second-stage helper: bytes appended to the tail of a PNG are extracted and planted into an arbitrary sibling package's directory on the installer's disk under the caller's chosen name. The exported symbol does not match the documented API, is named to obscure its purpose, and provides a primitive whose only use is smuggling payload bytes hidden inside an image into other node_modules entries.

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.

Malicious versions

3 flagged
1.0.11.0.21.0.3

Indicators of compromise (SHA-256)

97776a8746c6c0d75fee50594f26150e0a791d97ade2056c489c1ca8da0196ae
03bf564e2647cb828bb130eaaba71b21fb6d78928cb6e3a74165bbb2fc546b98
42312a6ef711b775012714a5fbd93495e09cd516ce4d6d60b606953b0018ac17
c28b141d06d34fafc2248d36cb28a08dd22e62a4e6ca90ebedfe179cb3e44ee6

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for module-relpath (3 malicious versions).

  2. If you installed it — respond

    Remove module-relpath from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If module-relpath was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. module-relpath on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pmg4-2q5x-v3x5IN-MAL-2026-019187IN-MAL-2026-019256IN-MAL-2026-019258

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks module-relpath-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

module-relpath (npm) malicious package — MAL-2026-14561 | O3 Security