Which versions of @dransay/address-validation are malicious?

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

How do I remediate @dransay/address-validation if I installed it?

@dransay/address-validation is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

If @dransay/address-validation 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/address-validation part of a known attack campaign?

Yes — @dransay/address-validation is associated with the IN-MAL-2026-021214 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/address-validation across my projects, lockfiles, and CI pipelines?

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

Malicious package

@dransay/address-validationnpm

Advisory published Oct 8, 2026Updated Oct 12, 2026

@dransay/address-validation is a confirmed malicious npm package (MAL-2026-17668) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @dransay/address-validation (npm)

MAL-2026-17668

Immediate action

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

npm uninstall @dransay/address-validation

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] declares a preinstall script (node beacon.js) that fires on npm install and performs a DNS lookup plus HTTPS GET to a subdomain of the Interactsh collaborator service oast.site with the path /address-validation. The implausibly high version number (99.0.0) and the preinstall callback are consistent with a dependency-confusion probe: any environment resolving this name reveals its egress IP and the package name to the operator of the collaborator host. No installer secrets, environment variables, or filesystem contents are read; the beacon transmits only install metadata (source IP, package name, DNS resolver). No code is fetched or executed from the remote host, and no persistence is established.

The OpenSSF Package Analysis project identified '@dransay/address-validation' @ 99.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

82ababa5637b2f53f5087a161eeba1b6ca6ddba6d31ebb7842614bf0da119fa7

189df4f2830e64a9cfbd0bed6ae8357aff16dc5496d83c3e5e4bd9457b536fa7

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @dransay/address-validation (version 99.0.0).
If you installed it — respond
@dransay/address-validation is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @dransay/address-validation 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/address-validation 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-021214

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @dransay/address-validation-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database