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

@inpeek/odatanpm

Advisory published Updated

@inpeek/odata is a confirmed malicious npm package (MAL-2026-17542) that opens a backdoor for remote access (malicious versions 99.99.99, 99.99.100, 99.99.101…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @inpeek/odata (npm)

MAL-2026-17542
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @inpeek/odata

What this malware does

@inpeek/[email protected] is a dependency-confusion placeholder published to the public npm registry on the unregistered @inpeek scope with an inflated version (99.99.100) designed to outrank any internal release of the same name. The package.json declares a postinstall lifecycle hook that executes ping.js on npm install. ping.js performs an unconditional HTTPS GET to the hardcoded collector URL https://webhook.site/bec9d4b2-8f49-451e-84be-2681cb91ebf2, passing the installer's hostname (os.hostname()), platform (os.platform()), and Node.js version (process.version) as query parameters. index.js throws on require, so any accidental consumer breaks loudly after the postinstall beacon has already fired. The package self-labels as a bug-bounty research placeholder, but the install-time dataflow — automatic transmission of installer host identifiers to a third-party collector the installer did not opt into — is the dependency-confusion exploitation shape and reaches any installer whose tooling resolves @inpeek/* from the public registry.

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

4 flagged
99.99.9999.99.10099.99.10199.99.102

Indicators of compromise (SHA-256)

3f7aeb131f69bd5b75c9420a8825c9621e89453f275bc1e198eb62d93400b5ae
dad085b4b3e089d6a6d4e6812c66a8b45f10d40bc4ab39ea7bd0ce850d17ed4b
5dd0a249ba1e978f084ca29dc0a5aca7b68da39a5510716ec5d7050bfd031647
af0f490d6d86c37f78a097c8bac2644d66355151bf051fae9bd5e1f021d0d6db
56d18a846606e6f829b3795f65d1991ad2e97c7d7b42b7e946e906b3e7d387f4

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for @inpeek/odata (4 malicious versions).

  2. If you installed it — respond

    @inpeek/odata establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If @inpeek/odata 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. @inpeek/odata on npm has been identified as a malicious package (versions 99.99.99, 99.99.100, 99.99.101, 99.99.102 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021003IN-MAL-2026-021005IN-MAL-2026-021029IN-MAL-2026-021004GHSA-cmm5-vwvx-cv5f

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @inpeek/odata-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

@inpeek/odata (npm) malicious package — MAL-2026-17542 | O3 Security