Which versions of @dransay/feature-flags are malicious?

The following npm versions of @dransay/feature-flags are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate @dransay/feature-flags if I installed it?

@dransay/feature-flags 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.

I already installed @dransay/feature-flags — how do I know if it already compromised me?

If @dransay/feature-flags 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.

Is @dransay/feature-flags part of a known attack campaign?

Yes — @dransay/feature-flags is associated with the IN-MAL-2026-021215 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @dransay/feature-flags across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @dransay/feature-flags (version 99.0.0).

Malicious package

@dransay/feature-flagsnpm

Advisory published Oct 8, 2026Updated Oct 12, 2026

@dransay/feature-flags is a confirmed malicious npm package (MAL-2026-17696) that opens a backdoor for remote access (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @dransay/feature-flags (npm)

MAL-2026-17696

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @dransay/feature-flags

What this malware does

@dransay/[email protected] is a dependency-confusion probe claiming the internal @dransay/* namespace, not an identified public package. Its preinstall hook runs on npm install as node beacon.js and sends a DNS lookup and an HTTPS GET to db3klhbi6i9hark1kegg174t38h33b6wt.oast.site, using the package name in the request; npm account 0xamino_hunter published it on 2026-10-08.

@dransay/[email protected] publishes a scoped name on the public npm registry at an inflated version (99.0.0) designed to win semver resolution against any private internal @dransay/* copy. package.json declares a preinstall hook node beacon.js; beacon.js unconditionally performs a DNS lookup and HTTPS GET to the hardcoded interactsh callback host db3klhbi6i9hark1kegg174t38h33b6wt.oast.site on every npm install, leaking the installer's public source IP, a timestamp, and confirmation that the scoped name resolved from the public registry to a third-party out-of-band interaction collector. The README self-describes the artifact as a probe of DrAnsay build infrastructure; author self-labeling as research does not change the install-time behavior for any environment whose npm resolves @dransay/* publicly.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

cc545bbb96903ee25218d8cab1a7d116d2ceb1ba64a3c929c79e56a6fc8e0585

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for @dransay/feature-flags (version 99.0.0).
If you installed it — respond
@dransay/feature-flags 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.
Did it already run?
If @dransay/feature-flags 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. @dransay/feature-flags on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021215

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder

Detect & block this

O3 blocks @dransay/feature-flags-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