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

@limebike/frontend-core-apinpm

Malicious code in @limebike/frontend-core-api (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4187
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @limebike/frontend-core-api

What this malware does

Package squats the @limebike npm scope and ships a preinstall/postinstall hook (node index.js) that, on npm install, collects hostname, non-internal network interface addresses, current working directory, directory listings of cwd / /app /../../ /../../../, and the contents of /app/package.json, then POSTs that JSON over plain HTTP to http://poc.khz.bar/install (index.js:46-52). README states 'Claimed by dphoeniixx', a handle associated with dependency-confusion research, but regardless of stated intent every installer whose CI mistakenly resolves the @limebike scope to the public registry leaks internal hostnames, internal network IPs, and the parent project's package.json to an attacker-controlled endpoint at install time.

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

1 flagged
85.14.48

Indicators of compromise (SHA-256)

ee42d28817c6c33d00e1bba45629091411b7d9591a5d941419f44e171cc99a58
36e6a8b7768f00cc5d468fe7a21f8792da1970b60e5ccbad17eefeda1a8d5b3d
b618d0f5ac281e7d5519398821805441039f8f0a79b46e206006007dbaa021d1

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @limebike/frontend-core-api (version 85.14.48). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @limebike/frontend-core-api across your stack and pipelines.

  2. If you installed it — respond

    Remove @limebike/frontend-core-api 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 @limebike/frontend-core-api was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @limebike/frontend-core-api before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @limebike/frontend-core-api on npm has been identified as a malicious package (version 85.14.48 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-89wg-7gqg-72xfIN-MAL-2026-003570IN-MAL-2026-003571

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @limebike/frontend-core-api-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.