DPD in Russia – Shipping for WooCommerce

woo-dpd · by dpdinrussia · wordpress.org ↗ · SVN ↗
Active installs
80
Current version
1.0.13
Added
2019-09-18
Last updated
2026-08-19 (1mo ago)
First seen by beacon
5mo ago
Total downloads
10,242

Statistics

2024-06-16 → 2026-09-09 · 786 days
Downloads today
2
7-day total 19
Week over week
▼ -37%
vs prior 7 days
30-day trend
flat
▲ +16% MoM
Abandonment
●○○○○
install base on one version
Downloads/day Linear trend
5441271402024-062024-102025-032025-072025-112026-04
251913602026-052026-052026-062026-062026-072026-08
251913602026-072026-082026-082026-082026-082026-09

Active versions

1.0
1.0 · 100.0%

Ratings

5★
2
4★
0
3★
0
2★
0
1★
2

Support: 0/0 resolved

Alerts (0)

No open alerts.

Show 1 resolved alert
Critical code_pattern Resolved · vendor_self_publishing_dpd_russia_courier 2026-05-08 16:16:55 (4mo ago)
Slugwoo-dpd
Patternhardcoded_ip_url
Kindbuiltin
Version1.0.11
Hit count1
First hit
File
lib/dpd-sdk/src/lib/API/Service/TrackingOrder.php
Line
13
Snippet
const TEST_API_URL = 'http://91.209.80.50:9090/ordertracking ';
Explanationplugin source hardcodes a raw IPv4 URL (e.g. `https://94.156.79.8/...`) — legitimate plugins use DNS hostnames because IPs change. Hardcoded IPs in plugin code are almost always either dev leftovers or attacker C2 infrastructure. The June 2024 social-warfare keylogger (audit #14) used `https://94.156.79.8/sc-top.js` for the JS payload host, `/AddSites` for victim registration, `/CMSUsers` for filesystem-recon exfil. Operator infrastructure on raw IPs avoids domain registration / RDAP detection paths. Post-filtered to skip RFC1918/loopback/link-local ranges and `vendor/`/`tests/` paths.
View raw JSON
{
    "slug": "woo-dpd",
    "pattern": "hardcoded_ip_url",
    "kind": "builtin",
    "version": "1.0.11",
    "hit_count": 1,
    "first_hit": {
        "file": "lib/dpd-sdk/src/lib/API/Service/TrackingOrder.php",
        "line": 13,
        "snippet": "const TEST_API_URL = 'http://91.209.80.50:9090/ordertracking ';"
    },
    "explanation": "plugin source hardcodes a raw IPv4 URL (e.g. `https://94.156.79.8/...`) \u2014 legitimate plugins use DNS hostnames because IPs change. Hardcoded IPs in plugin code are almost always either dev leftovers or attacker C2 infrastructure. The June 2024 social-warfare keylogger (audit #14) used `https://94.156.79.8/sc-top.js` for the JS payload host, `/AddSites` for victim registration, `/CMSUsers` for filesystem-recon exfil. Operator infrastructure on raw IPs avoids domain registration / RDAP detection paths. Post-filtered to skip RFC1918/loopback/link-local ranges and `vendor/`/`tests/` paths."
}

SVN committers (2)

Accounts with actual commit access to woo-dpd on plugins.svn.wordpress.org, reconstructed from svn log. This is the list that matters for ownership changes — not the readme contributors.

Committer Member since Commits First commit Latest commit
dpdinrussia Young account 2019-07-22 140 2019-09-18 · r2158281 2026-08-19 · r3654121
plugin-master 2007-03-09 1 2019-09-17 · r2157573 2019-09-17 · r2157573

Readme contributors (1)

Names the plugin's readme declares as contributors. A soft signal — anyone can be listed. The SVN access column is the ground-truth cross-reference: does this contributor actually commit code?

Contributor Member since SVN access Status
dpdinrussia 2019-07-22 140 commits Active