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

@drone-js-ext/corenpm

Advisory published Updated

@drone-js-ext/core is a confirmed malicious npm package (MAL-2026-18276) that opens a backdoor for remote access (malicious versions 1.0.0, 2.0.1, 3.0.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @drone-js-ext/core (npm)

MAL-2026-18276
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @drone-js-ext/core

What this malware does

The package ships a beacon.cjs that collects host identifiers (hostname, install path, current working directory, Node version) and POSTs them in cleartext to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. This beacon is wired to run automatically in two places: package.json declares scripts.postinstall = "node beacon.cjs", so it executes on npm install, and index.js also invokes the same fire() function at module load, so it executes again on require(). The remainder of the package is a no-op Proxy shim with no functional code matching the stated Compatibility shim description. The scope-and-version shape (@drone-js-ext/core at version 99.0.1 against a plausibly internal @drone-js-ext/* namespace) matches a dependency-confusion lure designed to be resolved in place of a private internal package. A README self-label of dependency-confusion test does not change the behavior: any installer that resolves this package has host-identifying data sent to a non-vendor, non-registry, bare-IP, plaintext-HTTP collector controlled by a third party.

Malicious versions

4 flagged
1.0.02.0.13.0.099.0.1

Indicators of compromise (SHA-256)

9173b1e0c1d01cafb58dfbcad8b59a50f49700cc911e22df2787f5a92b4c6e43

Detection & response playbook

Backdoor / remote access

  1. Find it

    Search your lockfiles and build artifacts for @drone-js-ext/core (4 malicious versions).

  2. If you installed it — respond

    @drone-js-ext/core 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 @drone-js-ext/core 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. @drone-js-ext/core on npm has been identified as a malicious package (versions 1.0.0, 2.0.1, 3.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021702

References

Credits

  • Amazon Inspector · finder
  • InvisiRisk, Inc. · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@drone-js-ext/core (npm) malicious package — MAL-2026-18276 | O3 Security